signals not handled correctly
Status: Beta
Brought to you by:
dboreham
If the target process is using signals (for example,
a multithreaded pthread application where one or more
threads are waiting on an event), a lsstack
attach/detatch process can cause a signal delivery
to be missed. lsstack isn't doing the right thing
(whatever that is) with signals while it's attached.
Logged In: YES
user_id=264605
It seems that this is a fundamental 2.4/linux threads issue.
Since we now have working 2.6/ntpl code, that doesn't
have this problem, we're not going to try to fix this for 2.4.