Re: [Toybox] fun with vfork

2016-10-13 Thread Rob Landley
On 10/13/2016 03:25 AM, Josh Gao wrote: > On Wed, Oct 12, 2016 at 5:49 PM, Rob Landley > wrote: > > So... no? I think? Is there a way _I_ can tag this? (I can't do my own > vfork prototype because I can't #undef the one I get out of unistd.h

Re: [Toybox] fun with vfork

2016-10-13 Thread Josh Gao
On Wed, Oct 12, 2016 at 5:49 PM, Rob Landley wrote: > > So... no? I think? Is there a way _I_ can tag this? (I can't do my own > vfork prototype because I can't #undef the one I get out of unistd.h and > that's a fairly generic header. It's sad I can't redo function > prototypes

Re: [Toybox] fun with vfork

2016-10-13 Thread Rob Landley
On 10/12/2016 12:09 PM, David R. Hedges wrote: > For what it's worth, your example (and the resulting symptom) seem to > fall squarely in this undefined territory from the vfork manpage / POSIX > description: >> the behavior is undefined if the process created by vfork() [..] calls >> any other

Re: [Toybox] fun with vfork

2016-10-12 Thread Rob Landley
On 10/11/2016 12:04 PM, Josh Gao wrote: > Do you have vfork tagged with __attribute__((returns_twice))? AFAIK, > that's the incantation to get gcc to do the right thing for setjmpy > functions. Do I have it tagged, or do you mean does glibc? (I didn't implement vfork, it came with libc.) Let's

Re: [Toybox] fun with vfork

2016-10-11 Thread Josh Gao
Do you have vfork tagged with __attribute__((returns_twice))? AFAIK, that's the incantation to get gcc to do the right thing for setjmpy functions. On Oct 11, 2016 4:23 AM, "Rob Landley" wrote: > While doing the rest of nommu support in netcat -L, I had some variant of: > >