RE: [dsdp-dd-dev] Gdb not killed after application terminates

["Marc Khouzam" <marc.khouzam@xxxxxxxxxxxx>]

Hi,

As part of bug http://bugs.eclipse.org/214384
it was decided to keep GDB running even after the debugging program exists by itself.  The idea is that
the user can still interact with GDB to get some information.  You can try this by typing command
to the GDB console even after the program is finished.

However, this did seem annoying in some cases, so the following was opened but not fixed yet:
http://bugs.eclipse.org/234468	There should be a preference to terminate debug session after the inferior process exits.

Marc

-----Original Message-----
From: dsdp-dd-dev-bounces@xxxxxxxxxxx on behalf of Ling.5.Wang@xxxxxxxxx
Sent: Tue 6/24/2008 2:30 AM
To: dsdp-dd-dev@xxxxxxxxxxx
Subject: [dsdp-dd-dev] Gdb not killed after application terminates
 
Hi,

I created a launch configuration of type "C/C++ Local Application
(Experimental -DSF)" on Linux, and started the debugger. One problem I
got is after the debugged application ran to the end and exited by
itself,  its process entry in Debug View was shown as terminated but the
"gdb" process was still running, leaving the "Launch" session live in
the Debug View. 

Is that a known bug or is there any special consideration behind that in
DSF ?

Thanks.

- Ling