Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: gdb-patches@sourceware.org
Subject: Re: [RFC] Support exec tracing on GNU/Linux and HP-UX
Date: Tue, 29 Jan 2008 22:54:00 -0000	[thread overview]
Message-ID: <20080129225317.GA21147@caradoc.them.org> (raw)
In-Reply-To: <20071019175920.GA548@caradoc.them.org>

On Fri, Oct 19, 2007 at 01:59:20PM -0400, Daniel Jacobowitz wrote:
> MontaVista's testing discovered some trouble with follow-fork.
> There's tests for this in the testsuite, but they're currently not
> run.  So the first thing this patch does is fix up foll-fork.exp
> to work on native GNU/Linux systems.
> 
> There's also tests for vfork and exec tracing.  Vfork tracing is
> currently supported in GDB but exec tracing is not, and the vfork
> testcase requires exec tracing anyway.  So I turned on exec tracing
> and removed some cruft that had built up since it was last used.

Now committed.  Thanks, Joel.

-- 
Daniel Jacobowitz
CodeSourcery


      parent reply	other threads:[~2008-01-29 22:53 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
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 [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=20080129225317.GA21147@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