public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Alex Bligh <alex@alex.org.uk>
To: Chuck Simmons <charles.simmons@oracle.com>,
		bartoschek@or.uni-bonn.de, gdb@sourceware.org
Cc: Alex Bligh <alex@alex.org.uk>
Subject: Re: Cannot fetch general-purpose registers for thread 1342445920:  generic error
Date: Fri, 01 Sep 2006 12:24:00 -0000	[thread overview]
Message-ID: <44F82684.2010404@alex.org.uk> (raw)
In-Reply-To: <20060901002026.GA22921@nevyn.them.org>

Daniel Jacobowitz wrote:

>> [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.

And for what it's worth, the 2 bugs I was seeing (one of
which had the same symptoms as the above) Daniel seems to
have fixed (the latter is AIUI awaiting commit to CVS).

Alex

  reply	other threads:[~2006-09-01 12:24 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-01  0:14 Chuck Simmons
2006-09-01  0:20 ` Daniel Jacobowitz
2006-09-01 12:24   ` Alex Bligh [this message]
  -- 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=44F82684.2010404@alex.org.uk \
    --to=alex@alex.org.uk \
    --cc=bartoschek@or.uni-bonn.de \
    --cc=charles.simmons@oracle.com \
    --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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).