From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 16542 invoked by alias); 27 Aug 2003 04:00:28 -0000 Mailing-List: contact gdb-patches-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sources.redhat.com Received: (qmail 16535 invoked from network); 27 Aug 2003 04:00:27 -0000 Received: from unknown (HELO nevyn.them.org) (66.93.172.17) by sources.redhat.com with SMTP; 27 Aug 2003 04:00:27 -0000 Received: from drow by nevyn.them.org with local (Exim 4.20 #1 (Debian)) id 19rrTv-00067k-55; Wed, 27 Aug 2003 00:00:27 -0400 Date: Wed, 27 Aug 2003 04:00:00 -0000 From: Daniel Jacobowitz To: Michael Snyder Cc: gdb-patches@sources.redhat.com, kettenis@gnu.org Subject: Re: RFA: lin-lwp cleanup Message-ID: <20030827040026.GA23492@nevyn.them.org> Mail-Followup-To: Michael Snyder , gdb-patches@sources.redhat.com, kettenis@gnu.org References: <20030826193221.GA1885@nevyn.them.org> <3F4C150F.8090802@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3F4C150F.8090802@redhat.com> User-Agent: Mutt/1.5.1i X-SW-Source: 2003-08/txt/msg00468.txt.bz2 On Tue, Aug 26, 2003 at 07:18:55PM -0700, Michael Snyder wrote: > Daniel Jacobowitz wrote: > >This patch doesn't do anything particularly important. I just moved some > >code from stop_wait_callback out to a new function. I thought I'd need it > >for my next patch; I turned out not to, but it's still cleaner this way. > > > >Also fixes the two small problems I asked Jeff about earlier today - an > >extra call to lin_lwp_thread_alive and a missing delete_thread. > > > >Is this OK? > > > > There's a bit more here than code movement -- the new code is not > identical to the old, even allowing for the jjohnstn changes. > > If you'll say a word or two about the differences, I expect I'll approve > them. The differences are exactly those two. There were two copies of the code which called delete_lwp, and one of them was missing delete_thread; so I collapsed them together. And there was a block which checked lin_lwp_thread_alive, now gone. Oh, I changed the text of the first error message from "exited" to "vanished" so that we could tell from the logs which case was used. -- Daniel Jacobowitz MontaVista Software Debian GNU/Linux Developer