From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gdb-patches-return-49782-listarch-gdb-patches=sources.redhat.com@sourceware.org>
Received: (qmail 23091 invoked by alias); 6 Jul 2007 13:18:48 -0000
Received: (qmail 23083 invoked by uid 22791); 6 Jul 2007 13:18:47 -0000
X-Spam-Check-By: sourceware.org
Received: from sibelius.xs4all.nl (HELO brahms.sibelius.xs4all.nl) (82.92.89.47)     by sourceware.org (qpsmtpd/0.31) with ESMTP; Fri, 06 Jul 2007 13:18:43 +0000
Received: from brahms.sibelius.xs4all.nl (kettenis@localhost.sibelius.xs4all.nl [127.0.0.1]) 	by brahms.sibelius.xs4all.nl (8.14.0/8.14.0) with ESMTP id l66DIbo6016471; 	Fri, 6 Jul 2007 15:18:37 +0200 (CEST)
Received: (from kettenis@localhost) 	by brahms.sibelius.xs4all.nl (8.14.0/8.14.0/Submit) id l66DIboI011998; 	Fri, 6 Jul 2007 15:18:37 +0200 (CEST)
Date: Fri, 06 Jul 2007 13:18:00 -0000
Message-Id: <200707061318.l66DIboI011998@brahms.sibelius.xs4all.nl>
From: Mark Kettenis <mark.kettenis@xs4all.nl>
To: drow@false.org
CC: gdb-patches@sourceware.org
In-reply-to: <20070706115802.GA10070@caradoc.them.org> (message from Daniel 	Jacobowitz on Fri, 6 Jul 2007 07:58:02 -0400)
Subject: Re: [commit] Fix bsd-uthread.c
References: <200707061139.l66BdnrB022359@brahms.sibelius.xs4all.nl> <20070706115802.GA10070@caradoc.them.org>
Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-patches.sourceware.org>
List-Subscribe: <mailto:gdb-patches-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-patches/>
List-Post: <mailto:gdb-patches@sourceware.org>
List-Help: <mailto:gdb-patches-help@sourceware.org>, <http://sourceware.org/ml/#faqs>
Sender: gdb-patches-owner@sourceware.org
X-SW-Source: 2007-07/txt/msg00107.txt.bz2

> Date: Fri, 6 Jul 2007 07:58:02 -0400
> From: Daniel Jacobowitz <drow@false.org>
> 
> 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.

Right