From: Daniel Jacobowitz <drow@false.org>
To: gdb-patches@sourceware.org
Subject: Re: [RFC] Support exec tracing on GNU/Linux and HP-UX
Date: Mon, 22 Oct 2007 20:01:00 -0000 [thread overview]
Message-ID: <20071022193024.GA16312@caradoc.them.org> (raw)
In-Reply-To: <20071022185627.GH764@adacore.com>
On Mon, Oct 22, 2007 at 11:56:27AM -0700, Joel Brobecker wrote:
> Actually, not so simple, because the EXEC event counts as
> one of the 2 events we expect during the startup phase. So the EXEC
> events must be activated at startup-time. The only option I can see
> at this point is to add a static global that is set during the startup
> phase, and would then cause the EXEC event to be translated into a
> SIGTRAP vulgaris when set. Another approach would be to have infrun
> treat EXEC events as SIGTRAPs during the startup phase. I don't think
> the second option is easier to implement (infrun needs to find out
> whether we're in the middle of startup or not, and then we need to
> redirect EXEC events into SIGTRAP events). What do you think of
> option 1?
Actually, I like option 2 better. Maybe we can push pending_execs
into a global similar to the (slightly different, though unused at
present) inferior_ignoring_leading_exec_events?
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2007-10-22 19:30 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-19 19:49 Daniel Jacobowitz
2007-10-22 6:01 ` Joel Brobecker
2007-10-22 12:09 ` Daniel Jacobowitz
2007-10-22 18:56 ` Joel Brobecker
2007-10-22 19:30 ` Joel Brobecker
2007-10-22 20:01 ` Daniel Jacobowitz [this message]
2007-12-21 16:04 ` Joel Brobecker
2007-12-21 16:13 ` Joel Brobecker
2008-01-29 17:09 ` Daniel Jacobowitz
2008-01-29 21:26 ` Joel Brobecker
2008-01-29 21:48 ` Daniel Jacobowitz
2008-01-29 21:48 ` Joel Brobecker
2008-01-29 22:17 ` Daniel Jacobowitz
2008-01-29 22:54 ` Daniel Jacobowitz
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=20071022193024.GA16312@caradoc.them.org \
--to=drow@false.org \
--cc=gdb-patches@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