Re: Cannot fetch general-purpose registers for thread 1342445920: generic error

[Daniel Jacobowitz <drow@false.org>]

On Thu, Aug 31, 2006 at 05:05:08PM -0700, Chuck Simmons wrote:
> 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.

Sorry, but this is basically useless as a bug report.  If you would
like GDB to be more reliable debugging your applications, you need
to provide us with enough information to reproduce and diagnose the
problem.  If you do, I'll be glad to take a look at it as soon as
time permits.

-- 
Daniel Jacobowitz
CodeSourcery