public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: Alexander Petukhov <devel@apetukhov.ru>
Cc: gdb@sourceware.org
Subject: Re: proper usage of "-exec-interrupt"
Date: Sat, 17 Sep 2011 19:06:00 -0000	[thread overview]
Message-ID: <20110917190624.GQ12670@adacore.com> (raw)
In-Reply-To: <4E7449BD.4030405@apetukhov.ru>

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

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.

-- 
Joel

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

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-17  7:17 Alexander Petukhov
2011-09-17 19:06 ` Joel Brobecker [this message]
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=20110917190624.GQ12670@adacore.com \
    --to=brobecker@adacore.com \
    --cc=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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).