From: Daniel Jacobowitz <drow@false.org>
To: Christoph Bartoschek <bartoschek@or.uni-bonn.de>
Cc: gdb@sourceware.org
Subject: Re: Cannot fetch general-purpose registers for thread 1342445920: generic error
Date: Tue, 20 Jun 2006 13:20:00 -0000 [thread overview]
Message-ID: <20060620130932.GA21490@nevyn.them.org> (raw)
In-Reply-To: <200606201456.57681.bartoschek@or.uni-bonn.de>
On Tue, Jun 20, 2006 at 02:56:57PM +0200, Christoph Bartoschek wrote:
> What are we doing?
>
> I am not sure what we are doing when the error occurs because instrumenting
> the code with printf is very tedious and stepping towards the error takes to
> long (maybe one could use a script that stepps forward till the error
> occurs). But the error seems to occur on different places: When a gzip job is
> forked and waited for, when threads are joined or when an exception is
> thrown. The exception case is not deterministic and seems to only occur when
> I use "catch throw".
I didn't mean "what is the program doing", I meant "what are you doing
with gdb". A session transcript might be helpful. I'm not sure what
catch throw could have to do with this, but that might be the trigger.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2006-06-20 13:09 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
2006-06-20 13:27 ` Christoph Bartoschek
2006-06-20 13:28 ` Daniel Jacobowitz
2006-06-20 16:21 ` Christoph Bartoschek
[not found] ` <20060620135351.GA9853@host0.dyn.jankratochvil.net>
2006-06-20 16:27 ` [filtered] " Christoph Bartoschek
2006-09-01 0:14 Chuck Simmons
2006-09-01 0:20 ` Daniel Jacobowitz
2006-09-01 12:24 ` Alex Bligh
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=20060620130932.GA21490@nevyn.them.org \
--to=drow@false.org \
--cc=bartoschek@or.uni-bonn.de \
--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