From: Paul Smith <paul@mad-scientist.net>
To: Pedro Alves <palves@redhat.com>, Simon Marchi <simon.marchi@polymtl.ca>
Cc: gdb@sourceware.org
Subject: Re: GDB (not) handling SIGINT...?
Date: Thu, 15 Nov 2018 18:01:00 -0000 [thread overview]
Message-ID: <6b62b6016ee54a525a4a78618be56b21f1e462df.camel@mad-scientist.net> (raw)
In-Reply-To: <276f4526-1873-0072-206c-c45bb47be3f6@redhat.com>
On Thu, 2018-11-15 at 16:24 +0000, Pedro Alves wrote:
> With current GDB, you can work around this by attaching in non-stop
> mode ("set non-stop on"), and then using "continue&" to continue in
> the background, and the "interrupt" command to interrupt.
Tricksy!
> If you're OK with hacking GDB, s/SIGINT/SIGSTOP/g in child_pass_ctrlc
> should work reasonably OK, even though not perfect.
Oh, I understand now. The SIGINT is passed to the child to get it to
stop. Somehow I assumed that there was a magical ptrace way to do
this, rather than having to send normal signals.
I guess there is now: using PTRACE_SEIZE instead of PTRACE_ATTACH,
which will allow you to later send PTRACE_INTERRUPT: presumably if this
were used would solve the problem for attached processes anyway...?
next prev parent reply other threads:[~2018-11-15 18:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-13 22:37 Paul Smith
2018-11-14 22:32 ` Simon Marchi
2018-11-15 13:55 ` Pedro Alves
2018-11-15 16:01 ` Paul Smith
2018-11-15 16:24 ` Pedro Alves
2018-11-15 18:01 ` Paul Smith [this message]
2018-11-15 18:04 ` Pedro Alves
2018-11-15 18:27 ` Paul Smith
2018-11-19 19:07 ` Paul Smith
2018-11-19 19:44 ` Paul Smith
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=6b62b6016ee54a525a4a78618be56b21f1e462df.camel@mad-scientist.net \
--to=paul@mad-scientist.net \
--cc=gdb@sourceware.org \
--cc=palves@redhat.com \
--cc=simon.marchi@polymtl.ca \
/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