<p>Use the <imgsrc="../images/command_link.png"alt=""><aclass="command-link"href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.cdt.dsf.gdb.ui.preferences)")'>GDB</a> preferences panel to control how the CDT debugger behaves when debugging with GDB,
<tdvalign="top"headers="description">When checked, the debug session will produce an additional console which will contain all the gdb/mi activity. Basically, this details the
interaction between the CDT debugger and GDB. This information is often critical when the debugger is not behaving as you expect. Turn this on and submit
<tdvalign="top"headers="option"><strong>Terminate GDB when last process exits</strong></td>
<tdvalign="top"headers="description">When checked, the CDT debugger will terminate the GDB host process after all the target processes it is debugging have terminated. Otherwise it will leave it running.</td>
<tdvalign="top"headers="description">When checked, hovering over an expression in the editor during a debug session will bring up an <em>enhanced</em> expression evaluation control. Otherwise, a more basic control is used. This, of course, assumes that you have the debugger's hovering capability turned on in C/C++ > Editor > Hovers. If not, this checkbox has no effect.<br>