From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 23912 invoked by alias); 10 Jul 2008 22:15:52 -0000 Received: (qmail 23904 invoked by uid 22791); 10 Jul 2008 22:15:52 -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; Thu, 10 Jul 2008 22:15:32 +0000 Received: from nan.false.org (localhost [127.0.0.1]) by nan.false.org (Postfix) with ESMTP id BCE5698415; Thu, 10 Jul 2008 22:15:30 +0000 (GMT) Received: from caradoc.them.org (22.svnf5.xdsl.nauticom.net [209.195.183.55]) by nan.false.org (Postfix) with ESMTP id 7ACAF98337; Thu, 10 Jul 2008 22:15:30 +0000 (GMT) Received: from drow by caradoc.them.org with local (Exim 4.69) (envelope-from ) id 1KH4QD-0004xJ-0q; Thu, 10 Jul 2008 18:15:29 -0400 Date: Thu, 10 Jul 2008 22:15:00 -0000 From: Daniel Jacobowitz To: Pedro Alves Cc: gdb-patches@sourceware.org Subject: Re: [non-stop] 08/10 linux native support Message-ID: <20080710221528.GA18013@caradoc.them.org> Mail-Followup-To: Pedro Alves , gdb-patches@sourceware.org References: <200806152205.49241.pedro@codesourcery.com> <200807101901.23598.pedro@codesourcery.com> <20080710195855.GA24287@caradoc.them.org> <200807102251.28066.pedro@codesourcery.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200807102251.28066.pedro@codesourcery.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-07/txt/msg00171.txt.bz2 On Thu, Jul 10, 2008 at 10:51:27PM +0100, Pedro Alves wrote: > Then, this patch cleaned it up a bit further. Basically, it gets > rid of the find_lwp_pid call in thread_db_find_new_threads. Instead > I'm using ALL_LWPS, which is already exported. This gets rid > of the find_lwp_pid -> linux_nat_lwp_pid rename throughout, and > removes the need for thread_db_find_new_threads_1. I then > reimported a couple of comments and cleanups that were on > the last patch, since you had picked up the previous-to-last. > > Otherwise, the logic is the same. > > Regtested on x86_64-unknown-linux-gnu. > > OK? Looks good to me. -- Daniel Jacobowitz CodeSourcery