From mboxrd@z Thu Jan 1 00:00:00 1970 From: bstell@ix.netcom.com To: Fernando Nasser Cc: insight Subject: Re: Insight freezes when trying to debug Mozilla Date: Wed, 04 Oct 2000 10:51:00 -0000 Message-id: <39DB6D63.1082B763@ix.netcom.com> References: <39D76A5E.773C5142@ix.netcom.com> <39DA433A.20ACB604@cygnus.com> <39DABF4D.27018510@ix.netcom.com> <39DAD2F3.2B7D4921@cygnus.com> <39DADB70.EBD7725@ix.netcom.com> <39DADD57.6188BB06@cygnus.com> X-SW-Source: 2000-q4/msg00010.html Fernando Nasser wrote: > ... > > > .... Unfortunately the STOP button > > > is dead because the Linux thread code fails to keep the GUI alive (a bug in that code, > > > at least for Insight purposes -- I will tell people on the gdb list about this). Could you tell me the name of the "gdb list"? > > > > This is the part I care about. Thanks. > > > > You're welcome. If I send a SIGSTOP to mozilla when the insight GUI freezes then mozilla stops and Insight unfreezes and reports a SIGSTP. It appears I can debug after this. This appears to be a work around. Thanks. > OK, so the "not keeping the GUI alive" is the problem. > > > > > > Use the second gdb "up" command and see > > > > > what is being done at lin-lwp.c:766 I would guess it is a waitpid() call. > > > > > You could see what the pid is, maybe trying sending it a SIGINT... > > > > > > > > Line 766 of lin-lwp.c is calling sigsuspend(). > >