Re: [dsdp-dd-dev] Cygwin gdb keeps running after debuggee finishesexecut

[Pawel Piech <pawel.piech@xxxxxxxxxxxxx>]

I think Dimitri is referring to the fact that GDB doesn't terminate just because the inferior process finishes.  We discussed this in the past, and there's a bug filed for it: 234468.

Cheers,
Pawel



Marc Khouzam wrote:

Normally, -gdb-exit is sent and GDB shoud exit.

In some cases, say the program is currently running, -gdb-exit won't work.

In those cases, at least on Linux we send a TERM signal and if that does not work, we send a KILL signal.

I'm not sure if it is the same code (org.eclipse.cdt.utils.spawner.Spawner) that runs on Windows, and how it deals with such signals.

If I get my hands on a windows mahcine, I'll try it, but I can't make promises.

 

Marc

---

From: dsdp-dd-dev-bounces@xxxxxxxxxxx [mailto:dsdp-dd-dev-bounces@xxxxxxxxxxx] On Behalf Of Dmitri Pikus
Sent: Wednesday, January 21, 2009 3:11 AM
To: Device Debugging developer discussions
Subject: [dsdp-dd-dev] Cygwin gdb keeps running after debuggee finishesexecution.

Hi All,

I noticed that Cygwin gdb keeps running after debuggee finishes execution (gdb.exe and starter.exe, that launches gdb, are not terminated).
This behavior doesn't cause us a problem at the current stage, I'm just curious if it's a configuration or some other issue.

Thanks!

Sincerely,
Dmitri Pikus

_______________________________________________
dsdp-dd-dev mailing list
dsdp-dd-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/dsdp-dd-dev