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
- From: Chuck Simmons <charles dot simmons at oracle dot com>
- To: bartoschek at or dot uni-bonn dot de, drow at false dot org, gdb at sourceware dot org
- Date: Thu, 31 Aug 2006 17:05:08 -0700
- Subject: Re: Cannot fetch general-purpose registers for thread 1342445920: generic error
Historically, in my experience, GDB has rarely handled threads well.
(There was a year or two about 10 to 15 years ago where things worked
fairly well, but since then...) Here is a short session on Suse Linux
using Posix threads:
"
(gdb) run 44123:127.0.0.1 dsk log.3382
Starting program: /home/csimmons/src/sysmon/sysmon2 44123:127.0.0.1 dsk
log.3382
[Thread debugging using libthread_db enabled]
[New Thread 1075110560 (LWP 31423)]
main: policy=2, prio=1
[New Thread 1077214128 (LWP 31426)]
ping_cpu: policy=2, prio=1
[New Thread 1079315376 (LWP 31427)]
Couldn't get registers: No such process.
"
This is probably a timing related bug in the implementation of GDB.
When debugging programs that spawn threads using back to back gdb
sessions, some runs will allow one to do debugging, and some runs won't.
Cs