There is a gdb log when debugging with Eclipse. What does it say?

Try running another debugger (say, ddd) and see what happens. They key, of course, is to eliminate variables. Try running with gdb alone.

Eclipse sometimes gets lost at a breakpoint presumably trying to load variable values. However, I've never lost UI control when this happens but have had to terminate the run or sometimes terminate Eclipse.

Is the machine frozen or is focus being held (sans cursor) somewhere? One advantage to running with two machines is the ability to ssh in and at least kill the running program. Can also be done from an Android phone. Saves having to reboot.

Unfortunately, submitting a bug doesn't mean anyone will act on it or even acknowledge its existence.. There are bugs listed that have been outstanding since forever. sometimes, though they are quietly corrected without a response in Bugzilla.

It's one of the problems with free open source: you are really on your own.

The gdb log is one of the consoles when debugging. There's a pull down menu to select it.

Hi Dave,
reading your report I'd like to raise a couple of simple points, hope it helps. First, from what you say it's only Eclipse that it's frozen, not the machine. If so, there is no need to reboot it, just kill eclipse from the console