From: Daniel Jacobowitz <drow@mvista.com>
To: gdb@sources.redhat.com
Subject: Re: Follow fork testcases?
Date: Sat, 11 Oct 2003 22:17:00 -0000 [thread overview]
Message-ID: <20031011221750.GA7209@nevyn.them.org> (raw)
In-Reply-To: <3F886E32.3080900@redhat.com>
On Sat, Oct 11, 2003 at 04:55:14PM -0400, Andrew Cagney wrote:
> Daniel,
>
> Should these be enabled? Do they work?
Follow-fork.exp works with some output changes. I haven't gotten
around to it yet because I want to test the updated tests on HP/UX.
It's on my TODO still.
Follow-vfork does not work because it also uses follow-exec
functionality. I need to ask for some comments on how following execs
SHOULD work, since the way it DOES work is somewhat dodgy. That's also
on my TODO list.
Thanks for the reminder.
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
prev parent reply other threads:[~2003-10-11 22:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-11 20:55 Andrew Cagney
2003-10-11 22:17 ` 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=20031011221750.GA7209@nevyn.them.org \
--to=drow@mvista.com \
--cc=gdb@sources.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