From: Daniel Jacobowitz <drow@false.org>
To: Michael Snyder <msnyder@redhat.com>
Cc: GDB Patches <gdb-patches@sources.redhat.com>
Subject: Re: [RFA] Run follow-fork tests on Linux
Date: Sat, 26 Nov 2005 04:03:00 -0000 [thread overview]
Message-ID: <20051125233347.GA10519@nevyn.them.org> (raw)
In-Reply-To: <4387914C.1000404@redhat.com>
On Fri, Nov 25, 2005 at 02:33:48PM -0800, Michael Snyder wrote:
> This allows the tests "foll-fork" and "foll-vfork" to run on Linux,
> where they mostly pass. A little more verbose output from linux-nat.c
> will fix the remaining failures.
What the others said, but...
> *************** proc vfork_parent_follow_to_bp {} {
> *** 109,115 ****
> }
> send_gdb "continue\n"
> gdb_expect {
> ! -re ".*Detaching after fork from process.*Breakpoint.*18.*$gdb_prompt "\
> {pass "vfork parent follow, to bp"}
> -re "$gdb_prompt $" {fail "vfork parent follow, to bp"}
> timeout {fail "(timeout) vfork parent follow, to bp" }
> --- 109,115 ----
> }
> send_gdb "continue\n"
> gdb_expect {
> ! -re ".*Detaching after fork from.*Breakpoint.*18.*$gdb_prompt "\
> {pass "vfork parent follow, to bp"}
> -re "$gdb_prompt $" {fail "vfork parent follow, to bp"}
> timeout {fail "(timeout) vfork parent follow, to bp" }
... you are testing this on something close to HEAD, right? That
shouldn't be printed unless "set debug linux-nat 1".
--
Daniel Jacobowitz
CodeSourcery, LLC
next prev parent reply other threads:[~2005-11-25 23:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-26 0:05 Michael Snyder
2005-11-26 3:58 ` Andreas Schwab
2005-11-28 8:26 ` Michael Snyder
2005-11-26 4:01 ` Mark Kettenis
2005-11-28 13:01 ` Michael Snyder
2005-11-26 4:03 ` Daniel Jacobowitz [this message]
2005-11-28 14:00 ` Michael Snyder
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=20051125233347.GA10519@nevyn.them.org \
--to=drow@false.org \
--cc=gdb-patches@sources.redhat.com \
--cc=msnyder@redhat.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