This is the mail archive of the
mailing list for the GDB project.
Re: proper usage of "-exec-interrupt"
- From: Joel Brobecker <brobecker at adacore dot com>
- To: Alexander Petukhov <devel at apetukhov dot ru>
- Cc: gdb at sourceware dot org
- Date: Sat, 17 Sep 2011 12:06:24 -0700
- Subject: Re: proper usage of "-exec-interrupt"
- References: <4E7449BD.firstname.lastname@example.org>
> Whay does this signal come to parent process and can I avoid this
This is a bit of a guess, since I don't remember all the details,
but I think it might be a question of process group. To implement
the interrupt, many targets simply send a SIGINT signal to the
inferior process group. If you spawned GDB within the same process
group as GDB, and both GDB and the program being debugged share
the same process group as well, the interrupt will cause SIGINT
to be received by your IDE as well. So, try spawning GDB in its
own process group.