From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 9286 invoked by alias); 5 Aug 2008 21:59:13 -0000 Received: (qmail 9277 invoked by uid 22791); 5 Aug 2008 21:59:13 -0000 X-Spam-Check-By: sourceware.org Received: from NaN.false.org (HELO nan.false.org) (208.75.86.248) by sourceware.org (qpsmtpd/0.31) with ESMTP; Tue, 05 Aug 2008 21:58:34 +0000 Received: from nan.false.org (localhost [127.0.0.1]) by nan.false.org (Postfix) with ESMTP id 2E25880001; Tue, 5 Aug 2008 21:58:32 +0000 (GMT) Received: from caradoc.them.org (22.svnf5.xdsl.nauticom.net [209.195.183.55]) by nan.false.org (Postfix) with ESMTP id 083BE983A9; Tue, 5 Aug 2008 21:58:32 +0000 (GMT) Received: from drow by caradoc.them.org with local (Exim 4.69) (envelope-from ) id 1KQUY3-00057F-0w; Tue, 05 Aug 2008 17:58:31 -0400 Date: Tue, 05 Aug 2008 21:59:00 -0000 From: Daniel Jacobowitz To: Ulrich Weigand Cc: gdb-patches@sourceware.org Subject: Re: [gdbserver] Problems trying to resume dead threads Message-ID: <20080805215831.GA19565@caradoc.them.org> Mail-Followup-To: Ulrich Weigand , gdb-patches@sourceware.org References: <20080804195434.GA28917@caradoc.them.org> <200808052105.m75L5FEJ003528@d12av02.megacenter.de.ibm.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200808052105.m75L5FEJ003528@d12av02.megacenter.de.ibm.com> User-Agent: Mutt/1.5.17 (2008-05-11) X-IsSubscribed: yes Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2008-08/txt/msg00093.txt.bz2 On Tue, Aug 05, 2008 at 11:05:15PM +0200, Ulrich Weigand wrote: > Daniel Jacobowitz wrote: > > On Mon, Aug 04, 2008 at 09:45:46PM +0200, Ulrich Weigand wrote: > > > I'd propose to just silently ignore ESRCH errors while writing registers > > > (in addition to your patch). What do you think? > > > > I think that's acceptable, though not ideal. ESRCH can mean "the > > program is gone", or for ptrace it can mean "the program is not > > stopped". So there are a class of bugs in gdbserver which can lead to > > the ESRCH error path. But distinguishing them from this case is quite > > difficult. > > The following patch implements this approach, fixing the problem for me. > Tested on powerpc-linux in local gdbserver mode. OK? Yes, this is OK. Thanks! -- Daniel Jacobowitz CodeSourcery