primitive-exit doesn't _exit

primitive-exit doesn't _exit

[Andrew Pimlott]

I thought that primitive-exit would call _exit(2) instead of
exit(3).  The reason is basically the same as for not calling scheme
unwind handlers: some library may have registered an atexit hook,
and you don't want this called in the forked process.

I think there needs to be some way to _exit.  primitive-exit seems
like the natural way to me, but if not there, perhaps in a new
function.

Andrew


_______________________________________________
Bug-guile mailing list
Bug-guile@gnu.org
http://mail.gnu.org/mailman/listinfo/bug-guile

Re: primitive-exit doesn't _exit

[Kevin Ryde]

Andrew Pimlott <andrew@pimlott.net> writes:
>
> I think there needs to be some way to _exit.  primitive-exit seems
> like the natural way to me, but if not there, perhaps in a new
> function.

Just to chuck in my two cents worth, I too think it'd be good to have
a _exit available.  This would help guile-gtk, since gtk recommends
that _exit be used in a child process after forking.

But I don't know if it should be primitive-exit doing this or a new
function.  I guess it depends whether there's a case for wanting C
level atexit cleanups but not scheme level unwinds.


_______________________________________________
Bug-guile mailing list
Bug-guile@gnu.org
http://mail.gnu.org/mailman/listinfo/bug-guile