From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 26478 invoked by alias); 2 Mar 2003 20:31:16 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 26471 invoked from network); 2 Mar 2003 20:31:16 -0000 Received: from unknown (HELO crack.them.org) (65.125.64.184) by 172.16.49.205 with SMTP; 2 Mar 2003 20:31:16 -0000 Received: from nevyn.them.org ([66.93.61.169] ident=mail) by crack.them.org with asmtp (Exim 3.12 #1 (Debian)) id 18pc0R-0005pL-00 for ; Sun, 02 Mar 2003 16:32:28 -0600 Received: from drow by nevyn.them.org with local (Exim 3.36 #1 (Debian)) id 18pa78-0006Us-00 for ; Sun, 02 Mar 2003 15:31:14 -0500 Date: Sun, 02 Mar 2003 20:31:00 -0000 From: Daniel Jacobowitz To: gdb@sources.redhat.com Subject: Re: expected behavior of GNU/Linux gcore and corefiles Message-ID: <20030302203114.GA24948@nevyn.them.org> Mail-Followup-To: gdb@sources.redhat.com References: <3E617797.5000704@redhat.com> <20030302033900.GA14335@nevyn.them.org> <20030302034653.GA14491@nevyn.them.org> <3E622998.5020104@redhat.com> <20030302170911.GA20234@nevyn.them.org> <3E624DEC.7040108@redhat.com> <20030302183257.GA21281@nevyn.them.org> <3E6263F8.7040706@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3E6263F8.7040706@redhat.com> User-Agent: Mutt/1.5.1i X-SW-Source: 2003-03/txt/msg00034.txt.bz2 On Sun, Mar 02, 2003 at 03:05:12PM -0500, Andrew Cagney wrote: > > >> > >>If that position means precluding certain native-only functionality? > > > > > >Not exactly; if that native-only functionality precludes keeping what > >we have now for non-thread_db setups and extending it. > > > > >For instance, I > >think we should always be able to print LWP state (assuming a 1-1 > >mapping when we have no thread_db to ask for more information). And I > >think we should add support for TLS based only on LWPs, since it's not > >dependent on the thread manager. If we can't "info mutex" on a cross > >corefile, well, that's the same as now. > > To draw this back to the original post. What of a native GDB loading > libthread-db over a core file to determine thread IDs and TLS? Well, it makes me pretty nervous - we (have to) load libthread_db from /lib. Not from solib-absolute-prefix. I have several setups where I debug core files from one machine on another. That said, I don't see any reason we shouldn't support it. We need to get it to work, of course. -- Daniel Jacobowitz MontaVista Software Debian GNU/Linux Developer