This is the mail archive of the
mailing list for the GDB project.
Re: thread cannot stop himself
- To: Nicolas Vignal <nicolas dot vignal at netline dot fr>
- Subject: Re: thread cannot stop himself
- From: Mark Kettenis <kettenis at wins dot uva dot nl>
- Date: 09 Feb 2001 12:36:07 +0100
- Cc: gdb at sources dot redhat dot com
- References: <01020814582000.18700@nicolas>
Nicolas Vignal <email@example.com> writes:
> I join a sample program with a thread who try to stop himself with a
> ( I know that is not the best way to do that ;-)
> It works fine in command line but not under gdb.
> gdb receive the signal and the flag pass to program is yes. But the thread
> never stop.
> Any idea of what happened ?
GDB uses SIGSTOP internally (for stopping threads) which interferes
horribly with your own use of the signal. I'm loooking into a
solution, but things are pretty hairy, and I can't guarantee that I
find an acceptable solution to the problem.
For now, the only advice I can give you is: don't use SIGSTOP. I'm
not sure what you're trying to accomplish by having a thread stop
itself, but there should be an alternative to using signals. Try
using a mutex, semaphore or perhaps poll/select.