undocumented vfork behaviour?

1999-08-26 Thread Andrew Gallatin
I'm working on getting linux/alpha compatability going in FreeBSD/alpha I stumbled over some odd fork behaviour that I was hoping somebody could shed some light on. Specifically, when a linux/alpha process forks, the child's return value is the parent's pid rather than zero. I tracked this

Re: undocumented vfork behaviour?

1999-08-26 Thread Bjoern Fischer
On Thu, Aug 26, 1999 at 10:40:29AM -0400, Andrew Gallatin wrote: [...] Specifically, when a linux/alpha process forks, the child's return value is the parent's pid rather than zero. [...] If I run the following code on FreeBSD/i386, I see: parent's pid = 6730 I am the child, result = 0 I

Re: undocumented vfork behaviour?

1999-08-26 Thread Terry Lambert
I'm working on getting linux/alpha compatability going in FreeBSD/alpha I stumbled over some odd fork behaviour that I was hoping somebody could shed some light on. Specifically, when a linux/alpha process forks, the child's return value is the parent's pid rather than zero. I tracked

Re: undocumented vfork behaviour?

1999-08-26 Thread Jason Thorpe
On Fri, 27 Aug 1999 02:20:52 + (GMT) Terry Lambert [EMAIL PROTECTED] wrote: This is a bug. ...but it's a bug in fork(), too. Not just vfork(). For other bugs in vfork(), look at the fact that the vacation program does not correctly deal with messages. ...fwiw, NetBSD fixed the

undocumented vfork behaviour?

1999-08-26 Thread Andrew Gallatin
I'm working on getting linux/alpha compatability going in FreeBSD/alpha I stumbled over some odd fork behaviour that I was hoping somebody could shed some light on. Specifically, when a linux/alpha process forks, the child's return value is the parent's pid rather than zero. I tracked this

Re: undocumented vfork behaviour?

1999-08-26 Thread Bjoern Fischer
On Thu, Aug 26, 1999 at 10:40:29AM -0400, Andrew Gallatin wrote: [...] Specifically, when a linux/alpha process forks, the child's return value is the parent's pid rather than zero. [...] If I run the following code on FreeBSD/i386, I see: parent's pid = 6730 I am the child, result = 0 I

Re: undocumented vfork behaviour?

1999-08-26 Thread Terry Lambert
I'm working on getting linux/alpha compatability going in FreeBSD/alpha I stumbled over some odd fork behaviour that I was hoping somebody could shed some light on. Specifically, when a linux/alpha process forks, the child's return value is the parent's pid rather than zero. I tracked

Re: undocumented vfork behaviour?

1999-08-26 Thread Jason Thorpe
On Fri, 27 Aug 1999 02:20:52 + (GMT) Terry Lambert tlamb...@primenet.com wrote: This is a bug. ...but it's a bug in fork(), too. Not just vfork(). For other bugs in vfork(), look at the fact that the vacation program does not correctly deal with messages. ...fwiw, NetBSD fixed the