From: Eli Zaretskii <eliz@gnu.org>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb@sources.redhat.com
Subject: Re: Switching to thread
Date: Fri, 09 May 2008 20:44:00 -0000 [thread overview]
Message-ID: <u8wyjmclp.fsf@gnu.org> (raw)
In-Reply-To: <20080509164248.GR7421@adacore.com>
> Date: Fri, 9 May 2008 09:42:48 -0700
> From: Joel Brobecker <brobecker@adacore.com>
> Cc: gdb@sources.redhat.com
>
> What happens in this case is that, after the new thread was created
> (and GDB resumed it without having switched to that thread), this new
> thread receives the SIGINT.
Right, I missed this. Thanks, this makes the situation clear.
next prev parent reply other threads:[~2008-05-09 20:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-09 7:53 Eli Zaretskii
2008-05-09 16:43 ` Joel Brobecker
2008-05-09 20:44 ` Eli Zaretskii [this message]
2008-05-09 19:20 ` Michael Snyder
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=u8wyjmclp.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=brobecker@adacore.com \
--cc=gdb@sources.redhat.com \
/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