From: Pedro Alves <palves@redhat.com>
To: Tristan Gingold <gingold@adacore.com>
Cc: John Gilmore <gnu@toad.com>, gdb@sourceware.org
Subject: Re: PR13901
Date: Wed, 04 Apr 2012 15:01:00 -0000 [thread overview]
Message-ID: <4F7C620C.6050809@redhat.com> (raw)
In-Reply-To: <454D631A-B8E3-42DD-860F-9B5F5A485810@adacore.com>
On 04/04/2012 03:47 PM, Tristan Gingold wrote:
> Welcome in the Darwin team :-)
;-)
> I was thinking about a slightly better way (IMHO): just call darwin_set_sstep when
> the single-step flag is set or was just cleared. This should improve performance.
> There might be subtile difference for signal handling, but I am not even sure that gdb behaviour is well defined in that case.
Hmm, good idea. Kernel's are known to forget the trace flag around signals and I'm under
the impression that darwin is one of those that can't step to signal handlers. But
indeed if we always single-step when the flag is set, and only "optimize" on
step->!step, it does sounds like it should work.
--
Pedro Alves
prev parent reply other threads:[~2012-04-04 15:01 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-30 13:42 PR13901 Jack Howarth
2012-03-30 14:19 ` PR13901 Tristan Gingold
2012-04-02 10:44 ` PR13901 Tristan Gingold
2012-04-02 11:57 ` PR13901 Tristan Gingold
2012-04-02 13:17 ` PR13901 Jack Howarth
2012-04-02 13:22 ` PR13901 Tristan Gingold
2012-04-02 13:56 ` PR13901 Pedro Alves
2012-04-02 14:07 ` PR13901 Tristan Gingold
2012-04-02 14:17 ` PR13901 Pedro Alves
2012-04-02 14:25 ` PR13901 Tristan Gingold
2012-04-02 14:59 ` PR13901 Andreas Schwab
2012-04-02 15:08 ` PR13901 Tristan Gingold
2012-04-02 15:23 ` PR13901 Pedro Alves
2012-04-02 16:22 ` PR13901 Andreas Schwab
2012-04-02 16:31 ` PR13901 Pedro Alves
2012-04-02 17:28 ` PR13901 Andreas Schwab
2012-04-03 7:28 ` PR13901 John Gilmore
2012-04-04 14:23 ` PR13901 Pedro Alves
2012-04-04 14:47 ` PR13901 Tristan Gingold
2012-04-04 15:01 ` Pedro Alves [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=4F7C620C.6050809@redhat.com \
--to=palves@redhat.com \
--cc=gdb@sourceware.org \
--cc=gingold@adacore.com \
--cc=gnu@toad.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).