Turns out the problem was the handlers for SIGUSR1 and SIGUSR2.
Once I removed them, everything worked ok.
 
I'm working in an embedded environment, and the thread implementation
is probably using these signals.  (A coworker tells me this was how
threads were implemented back in the day before they were cleaned 
up with the 2.6 kernel.)
_______________________________________________
busybox mailing list
[email protected]
http://lists.busybox.net/mailman/listinfo/busybox

Reply via email to