Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Chuck Simmons <charles.simmons@oracle.com>
To: bartoschek@or.uni-bonn.de, drow@false.org, gdb@sourceware.org
Subject: Re: Cannot fetch general-purpose registers for thread 1342445920:  generic error
Date: Fri, 01 Sep 2006 00:14:00 -0000	[thread overview]
Message-ID: <44F77934.3000305@oracle.com> (raw)

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


             reply	other threads:[~2006-09-01  0:14 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-01  0:14 Chuck Simmons [this message]
2006-09-01  0:20 ` Daniel Jacobowitz
2006-09-01 12:24   ` Alex Bligh
  -- strict thread matches above, loose matches on Subject: below --
2006-06-19 17:35 Christoph Bartoschek
2006-06-20 12:33 ` Daniel Jacobowitz
2006-06-20 13:00   ` Christoph Bartoschek
2006-06-20 13:20     ` Daniel Jacobowitz
2006-06-20 13:27       ` Christoph Bartoschek
2006-06-20 13:28         ` Daniel Jacobowitz
2006-06-20 16:21           ` Christoph Bartoschek

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=44F77934.3000305@oracle.com \
    --to=charles.simmons@oracle.com \
    --cc=bartoschek@or.uni-bonn.de \
    --cc=drow@false.org \
    --cc=gdb@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox