Re: SIGSTOP/SIGCONT problem ? (scheduler or make(1) ?)

Scott Long wrote:

>>
>
> I've had problems recently with SIGSTOP not being honored while
> compiling files.  Probably what happened here is that gcc continued
> on its merry way and exited when it was done compiling gencodes.o.
> Unfortunately I don't have much more debugging information to offer 


I've seen this but only with make.