From: Daniel Jacobowitz <drow@false.org>
To: Pedro Alves <pedro@codesourcery.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFC] 10/10 non-stop for linux native
Date: Wed, 25 Jun 2008 20:25:00 -0000 [thread overview]
Message-ID: <20080625200532.GG25575@caradoc.them.org> (raw)
In-Reply-To: <200805191621.08320.pedro@codesourcery.com>
On Mon, May 19, 2008 at 04:21:08PM +0100, Pedro Alves wrote:
> One issue I would like comments on, is that
> -exec-continue / target_stop_ptid relies on an event happening
> on the inferior. Should we not rely on that, and just suspend
> the thread with SIGSTOP ? Would this affect frontends ?
About this: don't play with SIGSTOP. It has pretty complicated
effects, for instance stopping entire thread groups and cancelling
pending job control signals. While working on attach-to-stopped
support a few months ago Roland educated me in the gritty details.
SIGINT isn't great, but with ptrace it's our most plausible option.
--
Daniel Jacobowitz
CodeSourcery
prev parent reply other threads:[~2008-06-25 20:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-06 18:31 Pedro Alves
2008-05-08 18:30 ` Eli Zaretskii
2008-05-09 3:25 ` Pedro Alves
2008-05-09 22:10 ` Michael Snyder
2008-05-10 2:54 ` Pedro Alves
2008-05-19 17:20 ` Pedro Alves
2008-06-25 20:25 ` Daniel Jacobowitz [this message]
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=20080625200532.GG25575@caradoc.them.org \
--to=drow@false.org \
--cc=gdb-patches@sourceware.org \
--cc=pedro@codesourcery.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