Re: SIGSEGV after vfork()

Jakub Jelinek (jj@sunsite.ms.mff.cuni.cz)
Fri, 19 Mar 1999 21:32:31 +0100 (CET)

>
> The program attached below causes a SIGSEGV signal in parent, no matter
> of what child does (exit() or execve()).
>
>
> If the wrapper routine vfork() is made inline, the fault does not occur;
> however, the fault always occurs if ``exit(0)'' is replaced by ``return''.
> In short:
>
> Am I missing something? Is it a kernel problem?

Yep, you miss a point that vfork requires special care dependent on the
architecture. Have a look at glibc-2.1 and grab vfork.S from
sysdeps/unix/sysv/linux/<yourarch>/vfork.S.
It is not a kernel problem.

Cheers,
Jakub
___________________________________________________________________
Jakub Jelinek | jj@sunsite.mff.cuni.cz | http://sunsite.mff.cuni.cz
Administrator of SunSITE Czech Republic, MFF, Charles University
___________________________________________________________________
UltraLinux | http://ultra.linux.cz/ | http://ultra.penguin.cz/
Linux version 2.2.3 on a sparc64 machine (3958.37 BogoMips)
___________________________________________________________________

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/