Re: gdb, threads, and Red Hat Linux 6.2

[Mark Kettenis]

Tom Tromey <address@hidden> writes:

> I'm using x86 Red Hat Linux 6.2 and the latest cvs gdb (I updated
> earlier today).
> 
> I'm debugging a Java program (which therefore uses threads).
> 
> Every time I `next' I get this:
> 
>     (gdb) n
>     Using pending wait status for LWP 26660.
>     Received CPU time limit exceeded in LWP 26660 while waiting for SIGSTOP.
>     11            String z = ("z" + fred ()).intern ();
>     (gdb) 
>     Using pending wait status for LWP 26660.
>     12            System.out.println (z);
> 
> Are these `pending wait' messages useful?  Intentional?
> What about the CPU time limit message?

They're debugging messages.  The CPU time limit message means that
your program got a SIGXCPU in an interval where GDB had sent it a
SIGSTOP and was waiting for it to report back.  That's a debugging
message too by the way.

> I'd rather not see them.  Is there a way to disable them?

You can #undef DEBUG in lin-lwp.c.

The debug messages are still enabled since this code is still somewhat
experimental, and even though it has been in since half September I
still haven't got a terrible amount of feedback.  I still suspect this
code is somehwat fragile, since the minimalistic threads support in
the Linux kernel makes us jump through quite a number of hoops.  But
perhaps now's the time to disable those messages.

Mark