[uClibc]Re: [BusyBox] Re: BusyBox `msh' doesn't work correctly with vfork / uClibc

Miles Bader miles at gnu.org
Tue Mar 5 20:52:30 UTC 2002


Stefan Soucek <ssoucek at coactive.com> writes:
> > However, Stefan's patch doesn't address the problem with `exit' that
> > I reported, so my patch (that changes things to use `_exit') or
> > something similar is still necessary.
> 
> I obviously missed those parts. I don't know why our shell doesn't crash
> on them but maybe they never get activated.

I use msh with uClibc, and the internals of uClibc's exit handling were
changed recently in a way that causes problems if a program manages to
exit twice.  Perhaps on your system, it's harmless to do so (the usual
problem with calling exit from vfork is stdio junk, but I guess msh
doesn't use stdio(?)).

[Of course to trigger the problem exec has to fail, so things will also
probably be fine as long as never make any typing mistakes.  :-) ]

Cheers,

-Miles
-- 
Next to fried food, the South has suffered most from oratory.
  			-- Walter Hines Page



More information about the uClibc mailing list