Bug in current CVS

Bug in current CVS

[Tom Tromey]

I'm using the current CVS trunk gdb on my x86 Red Hat Linux 6.2 box.
I somehow got gdb into a state where attempts to re-run the inferior
or to exit gdb fail like so:

    (gdb) r
    The program being debugged has been started already.
    Start it from the beginning? (y or n) y
    Cannot find thread 1024: generic error
    (gdb) q
    A debugging session is active.
    Do you still want to close the debugger?(y or n) y
    Cannot find thread 1024: generic error

I finally had to C-z gdb and kill it from the shell.

If it matters, the program I was debugging used threads.

I don't know how I got gdb into this state :-(.

Tom

Re: Bug in current CVS

[Kimball Thurston]

I'm not sure if it helps, but I was able to get this to happen every
time when I was poking around with the multi-thread problems with
dlopen - I added a stupid cache to thread_db_thread_alive to see how
much it would help runtime performance, knowing my threads wouldn't
die for the test I was running. However, at exit this of course fouls
things up, and I got this error message every time, so maybe the
thread db is getting confused?

- K

At 22 Oct 2001 18:57:05 -0600,
Tom Tromey wrote:
> 
> I'm using the current CVS trunk gdb on my x86 Red Hat Linux 6.2 box.
> I somehow got gdb into a state where attempts to re-run the inferior
> or to exit gdb fail like so:
> 
>     (gdb) r
>     The program being debugged has been started already.
>     Start it from the beginning? (y or n) y
>     Cannot find thread 1024: generic error
>     (gdb) q
>     A debugging session is active.
>     Do you still want to close the debugger?(y or n) y
>     Cannot find thread 1024: generic error
> 
> I finally had to C-z gdb and kill it from the shell.
> 
> If it matters, the program I was debugging used threads.
> 
> I don't know how I got gdb into this state :-(.
> 
> Tom
>