public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "luto at mit dot edu" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/14559] New: The 'interrupt' command does not work if sigwait is in use
Date: Fri, 07 Sep 2012 19:09:00 -0000 [thread overview]
Message-ID: <bug-14559-4717@http.sourceware.org/bugzilla/> (raw)
http://sourceware.org/bugzilla/show_bug.cgi?id=14559
Bug #: 14559
Summary: The 'interrupt' command does not work if sigwait is in
use
Product: gdb
Version: unknown
Status: NEW
Severity: normal
Priority: P2
Component: gdb
AssignedTo: unassigned@sourceware.org
ReportedBy: luto@mit.edu
Classification: Unclassified
Take a program that uses sigwait (on Linux). Invoke gdb. Start the program
with r&, so it's running asynchronously. Then type 'interrupt'. It doesn't
work -- sigwait reports SIGINT. IMO this is a separate gdb bug from the usual
bugs about SIGINT and sigwait not getting along (e.g. bug 9425): the interrupt
command should be directly stopping the program, not sending SIGINT.
--
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
next reply other threads:[~2012-09-07 19:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-07 19:09 luto at mit dot edu [this message]
2012-09-11 15:22 ` [Bug gdb/14559] " jan.kratochvil at redhat dot com
2012-09-11 15:28 ` palves at redhat dot com
2012-09-11 21:46 ` luto at mit dot edu
2013-11-26 20:41 ` tromey at redhat dot com
2014-07-30 17:11 ` dje at google dot com
2021-10-21 7:03 ` crystalrubytails at gmail dot com
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=bug-14559-4717@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=gdb-prs@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).