From: Pedro Alves <pedro@codesourcery.com>
To: gdb-patches@sourceware.org
Cc: "Ulrich Weigand" <uweigand@de.ibm.com>
Subject: Re: [rfc v2][rft (procfs, nto-procfs)] Fix signal bypass heuristic with software single-step
Date: Mon, 04 Apr 2011 09:47:00 -0000 [thread overview]
Message-ID: <201104041047.44630.pedro@codesourcery.com> (raw)
In-Reply-To: <201103311911.p2VJBn27015944@d06av02.portsmouth.uk.ibm.com>
On Thursday 31 March 2011 20:11:49, Ulrich Weigand wrote:
> Pedro Alves wrote:
>
> > Might be we just need to check if _any_ thread is stepping, when
> > deciding whether to tell the target to report back all signals?
>
> I've thought about this a bit more. The primary cause why we need
> to tell the target to report back all signals is because we have
> pulled out breakpoints to step over one -- this is why running
> arbitrary signal handlers would be dangerous.
...
> Thoughts?
This makes sense to me. Thanks for thinking this through.
The patch looked okay to me.
--
Pedro Alves
next prev parent reply other threads:[~2011-04-04 9:47 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-19 1:54 [rfc][rft " Ulrich Weigand
2011-03-22 17:25 ` Pedro Alves
2011-03-24 16:39 ` Ulrich Weigand
2011-03-31 19:42 ` [rfc v2][rft " Ulrich Weigand
2011-04-04 9:47 ` Pedro Alves [this message]
2011-04-05 19:22 ` Ulrich Weigand
2011-04-05 19:33 ` Aleksandar Ristovski
2011-04-05 22:56 ` Ulrich Weigand
2011-04-06 1:37 ` Aleksandar Ristovski
2011-04-06 17:00 ` Ulrich Weigand
2011-04-26 17:34 ` Ulrich Weigand
2011-04-06 6:07 ` Joel Brobecker
2011-04-06 17:01 ` Ulrich Weigand
2011-04-27 1:12 ` Joel Brobecker
2011-04-27 13:31 ` Ulrich Weigand
2011-03-22 17:37 ` [rfc][rft " Tom Tromey
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=201104041047.44630.pedro@codesourcery.com \
--to=pedro@codesourcery.com \
--cc=gdb-patches@sourceware.org \
--cc=uweigand@de.ibm.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