This is the mail archive of the mailing list for the GDB project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: gdbserver/gdb-6/4 and lots of pthreads

On Fri, Nov 17, 2006 at 03:01:01PM -0500, wrote:
> >On Fri, Nov 17, 2006 at 01:46:56PM -0500, wrote:
> >>Sending packet:
> >>
> $QPassSignals:e;10;11;13;14;17;18;1a;1b;1c;1e;1f;20;21;24;25;4c;#af...Ack
> >
> >Ignore signal 0xe.  In the GDB remote protocol that is SIGALRM.
> >
> I had "handle SIGALRM nostop noprint" in my .gdbinit file  I had added 
> that while
> digging into this problem a while ago and had forgotten about it.  
> Removing it
> and re-running everything doesn't appear to have an effect.  In 

That's the default, so it should make no difference.

> This is the CVS version from Wednesday evening, with your patch 
> contained here:

That should be fine.  But update to today's CVS with no extra patches
just to be sure.

If it's still doing this, then I would recommend a debugging printf in
linux-low.c, right before the new if statement with the pass_signals[]
check.  pass_signals[target_signal_from_host (WSTOPSIG (wstat))] ought
to be set for SIGALRM, and we ought not to return it to GDB, but your
log says we did that.

Daniel Jacobowitz

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]