Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Alexander Petukhov <devel@apetukhov.ru>
To: gdb@sourceware.org
Subject: proper usage of "-exec-interrupt"
Date: Sat, 17 Sep 2011 07:17:00 -0000	[thread overview]
Message-ID: <4E7449BD.4030405@apetukhov.ru> (raw)

Hi,
I'm writing a GDB plugin for an IDE and I'm using async target in MI mode
to allow user to alter breakpoints while debugging.
As I learned I have to use "-exec-interrupt" command to stop a debugger but
when I'm doing so a process that spawns GDB, i.e. an IDE receives SIGINT 
and exits accordingly.
Unfortunately I wasn't able to intercept a signal in IDE as it's written 
with GTK and signal functions do not work for some reason.
The other way I've found is to send SIGINT directly to a GDB process and 
it worked for me but
recently another developer reported that he has problem with finishing 
the whole X session when trying to interrupt GDB in this way, looks like 
SIGINT reached X session manager...

Whay does this signal come to parent process and can I avoid this somehow?

Thanks, Alexander


             reply	other threads:[~2011-09-17  7:17 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-17  7:17 Alexander Petukhov [this message]
2011-09-17 19:06 ` Joel Brobecker
2011-09-19 14:13   ` Alexander Petukhov

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4E7449BD.4030405@apetukhov.ru \
    --to=devel@apetukhov.ru \
    --cc=gdb@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox