[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: monit deadlock
From: |
Jan-Henrik Haukeland |
Subject: |
Re: monit deadlock |
Date: |
Wed, 17 Sep 2003 23:24:06 +0200 |
User-agent: |
Gnus/5.1002 (Gnus v5.10.2) XEmacs/21.4 (Reasonable Discussion, linux) |
Martin Pala <address@hidden> writes:
> (gdb) set stopped=1
> (gdb) print stopped
> $3 = 1
> (gdb) continue
> Continuing.
> Program exited normally.
> (gdb)
Hmm, I'm not sure. We use lots of signal blocks (which is good), but
here the TERM signal must have been blocked so do_destroy could not be
called. Try to move the 'do_signal_block();' from main() into
do_destroy *after* Run.stopped= TRUE;
Does it help?
--
Jan-Henrik Haukeland
- monit deadlock, Martin Pala, 2003/09/17
- Re: monit deadlock, Martin Pala, 2003/09/17
- Re: monit deadlock,
Jan-Henrik Haukeland <=
- Re: monit deadlock, Martin Pala, 2003/09/17
- Re: monit deadlock, Martin Pala, 2003/09/17
- Re: monit deadlock, Jan-Henrik Haukeland, 2003/09/17
- Re: monit deadlock, Jan-Henrik Haukeland, 2003/09/17
- Re: monit deadlock, Martin Pala, 2003/09/17
- Re: monit deadlock, Jan-Henrik Haukeland, 2003/09/17