This is the mail archive of the
gdb@sourceware.org
mailing list for the GDB project.
Re: Cannot fetch general-purpose registers for thread 1342445920: generic error
Am Dienstag, 20. Juni 2006 15:27 schrieb Daniel Jacobowitz:
> On Tue, Jun 20, 2006 at 03:24:44PM +0200, Christoph Bartoschek wrote:
> > Ok, here is a transcript of a session:
>
> So: attach to a running process, continue for a while, then when it
> creates threads gdb breaks.
>
> > Program received signal SIGUSR2, User defined signal 2.
> > 0x00002aaaaacd1189 in raise () from /lib64/tls/libpthread.so.0
> > (gdb)
> > Continuing.
> > [New Thread 1342445920 (LWP 3980)]
> > [Thread 1342445920 (LWP 3980) exited]
> > [New Thread 1342445920 (LWP 3981)]
> > [Thread 1342445920 (LWP 3981) exited]
> > [New Thread 1141119328 (LWP 3982)]
> > [Thread 1141119328 (LWP 3982) exited]
> > Cannot fetch general-purpose registers for thread 1141119328: generic
> > error (gdb)
>
> That thread's already "exited". Hmm. Is your application continuing
> to receive asynchronous signals at this point? i.e. is it possible
> that we stopped while the thread was exiting, because of a SIGUSR2?
The SIGUSR2 are only emitted when a new .dll is loaded to give the user the
opportunity to set breakpoints. However when the new threads are starting
loading of libraries has finished and no new SIGUSR2 are generated anymore.
Additionally the application does not start any child here such that no
SIGCHLD is possible.
Normally I would say that no asynchronous signals are sent to the application
after the last SIGUSR2.
BTW, thread 1141119328 has been finished after an exception has been caught in
the function given to pthread_create. Normally this should be no problem.
Christoph Bartoschek