From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 22692 invoked by alias); 16 Dec 2001 20:26:11 -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 22388 invoked from network); 16 Dec 2001 20:24:54 -0000 Received: from unknown (HELO nevyn.them.org) (128.2.145.6) by sources.redhat.com with SMTP; 16 Dec 2001 20:24:54 -0000 Received: from drow by nevyn.them.org with local (Exim 3.33 #1 (Debian)) id 16Fhpo-0001LZ-00; Sun, 16 Dec 2001 15:24:32 -0500 Date: Sun, 16 Dec 2001 12:26:00 -0000 From: Daniel Jacobowitz To: Andrew Cagney Cc: Michael Snyder , gdb-patches@sources.redhat.com Subject: Re: [RFA] Don't use thread_db on corefiles Message-ID: <20011216152432.A4182@nevyn.them.org> Mail-Followup-To: Andrew Cagney , Michael Snyder , gdb-patches@sources.redhat.com References: <20011213180259.A11251@nevyn.them.org> <3C1933E7.E2B9DE87@cygnus.com> <20011213181006.A11536@nevyn.them.org> <3C193D13.AED0F79F@cygnus.com> <20011213185635.A12902@nevyn.them.org> <3C19543A.2580D12E@cygnus.com> <20011213232557.B20920@nevyn.them.org> <3C1AB5EE.1000506@cygnus.com> <20011214214103.A3900@nevyn.them.org> <3C1B854E.1000702@cygnus.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3C1B854E.1000702@cygnus.com> User-Agent: Mutt/1.3.23i X-SW-Source: 2001-12/txt/msg00410.txt.bz2 On Sat, Dec 15, 2001 at 12:15:58PM -0500, Andrew Cagney wrote: > >Hmm, perhaps it is a native GDB looking at a threaded core file? In > >>that case, yes the thread-db should drop its self on top. If that is > >>causing an internal error then there is something messed up that should > >>be fixed. > > > > > >Yes, that's where the internal error is. They're based on the fact > >that thread-db tries to enable event reporting, as best I can tell. > > > Sounds like that is the bug to fix. Enabling event reporting probably > doesn't make much sense when the target is lifeless. I was about to try a patch for this when I realized that my primary objection still holds. This only works if you're debugging on a very similar host to the one the core was dumped on. If you've got, say, a glibc 2.1.3 host and are looking at a glibc 2.2.3 core... well, you can provide target libraries and make GDB use those, but there's no way to provide a cross libthread_db. Are we really comfortable with that? This'll probably cause GDB to misbehave in arbitrarily unpredictable ways in that circumstance. And we've no way to detect it that I can see. -- Daniel Jacobowitz Carnegie Mellon University MontaVista Software Debian GNU/Linux Developer