This is the mail archive of the
frysk@sourceware.org
mailing list for the frysk project.
Re: vfork thoughts
- From: Tom Tromey <tromey at redhat dot com>
- To: Phil Muldoon <pmuldoon at redhat dot com>
- Cc: frysk at sourceware dot org
- Date: Thu, 19 Jun 2008 19:11:52 -0600
- Subject: Re: vfork thoughts
- References: <48565AD5.8050902@redhat.com>
- Reply-to: Tom Tromey <tromey at redhat dot com>
Phil> If anyone has a real life use case for debugging a vfork scenario we
Phil> could model, that would help also.
gcc uses vfork when spawning child processes. And, the code that
actually does this does do some work between the vfork and the exec --
it is extremely common to move file descriptors around here. So, if
you want to debug in this region, or just want to debug child
processes created by vfork, gcc works :). There are probably a lot of
other examples like this.
Tom