From: Daniel Jacobowitz <drow@false.org>
To: Mark Kettenis <mark.kettenis@xs4all.nl>
Cc: gdb-patches@sourceware.org
Subject: Re: [commit] Fix bsd-uthread.c
Date: Fri, 06 Jul 2007 11:58:00 -0000 [thread overview]
Message-ID: <20070706115802.GA10070@caradoc.them.org> (raw)
In-Reply-To: <200707061139.l66BdnrB022359@brahms.sibelius.xs4all.nl>
On Fri, Jul 06, 2007 at 01:39:49PM +0200, Mark Kettenis wrote:
> This fixes the problem with threads debugging I reported a few days
> ago. The problem is that the code reads from target memory to look up
> the thread ID. This used to be ago, since if reading from the live
> target failed, it would read from the object file, and things would be
> ok (even though what it read from the object file was probably just a
> bunch of zeroes). However, with the change that Daniel recently made,
> that no longer happens, error() gets called, and we end up in a
> hopelessly confused state.
This is at the tail end of wait, i.e. before we've popped the current
target, right? Thanks, I see why it broke now.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2007-07-06 11:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-06 12:05 Mark Kettenis
2007-07-06 11:58 ` Daniel Jacobowitz [this message]
2007-07-06 13:18 ` Mark Kettenis
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=20070706115802.GA10070@caradoc.them.org \
--to=drow@false.org \
--cc=gdb-patches@sourceware.org \
--cc=mark.kettenis@xs4all.nl \
/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