Re: second try, defunct processes

[Aaron Solochek <aarons@andrew.cmu.edu>]

Well, I tried 2.7.2, and although it seemed to last a little longer,
this morning I wake up, and it didn't help.  Any other ideas?  Would
wiping the system clean and trying again help?

-Aaron Solochek
 leko@cmu.edu


Grendel wrote:
> 
> * Ben Collins said:
> [snip]
> > > by using waitpid or wait4) the child process will go zombie (<defunct>). If
> > > the application is coded properly and it still happens, it might mean that
> > > the kernel fails to deliver the SIGCHLD signal to the parent for some
> > > reason. It might be caused by the kernel compiled with 2.95.x gcc.
> > > Generally, it's safer to use gcc 2.7.2.3 to compile your kernels.
> >
> > That would be true except this is sparc, and 2.7.2.3 can create some buggy
> > code for sparcs.
> I don't know much about sparcs & Linux, I just remember having a similar
> problem on x86 with a kernel compiled using 2.95.1 (AFAIR) that optimized
> the kernel code so much, it failed to deliver some signals. Situation was
> pretty much the same.
> 
> marek
> 
>   ------------------------------------------------------------------------
>    Part 1.2Type: application/pgp-signature