From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 3544 invoked by alias); 15 Dec 2001 02:42:19 -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 3108 invoked from network); 15 Dec 2001 02:41:03 -0000 Received: from unknown (HELO nevyn.them.org) (128.2.145.6) by sources.redhat.com with SMTP; 15 Dec 2001 02:41:03 -0000 Received: from drow by nevyn.them.org with local (Exim 3.33 #1 (Debian)) id 16F4l5-00012B-00; Fri, 14 Dec 2001 21:41:03 -0500 Date: Fri, 14 Dec 2001 18:42: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: <20011214214103.A3900@nevyn.them.org> Mail-Followup-To: Andrew Cagney , Michael Snyder , gdb-patches@sources.redhat.com References: <20011213152958.A30211@nevyn.them.org> <3C1931E3.E240B409@cygnus.com> <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> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3C1AB5EE.1000506@cygnus.com> User-Agent: Mutt/1.3.23i X-SW-Source: 2001-12/txt/msg00393.txt.bz2 On Fri, Dec 14, 2001 at 09:31:10PM -0500, Andrew Cagney wrote: > >Oh, is that what you were talking about? Sorry, I must have been > >>confused. > >> > >>So -- you are talking about building a single GDB that can debug > >>1) native x86 linux, and > >>2) MIPS multi-threaded linux corefiles. > >> > >>Is that right? > > > > > >Well, that's not actually something I need to do, but I'd like it to be > >possible. I only need for both native and cross-hosted debuggers to > >both be able to get at the core files. But as things stand now, if we > >fix thread_db to be able to do so using lin-lwp, then the native and > >cross debuggers will get at the threads using completely different > >interfaces. That worries me. > > > At a technical level, it would mean making the thread:lwp mapping > library multi-arch. I think Michael gave a good summary - that isn't a > free lunch. (1) > > Returning to the problem at hand though, > > If you build --target=mips-unknown-linux-gnu does the resultant GDB > include the native thread-db code? Surely it doesn't since, as you > point out, it can't work. For the moment, would only be able to display > threads, just the raw LWPs. Indeed, it doesn't include thread-db. It displays only the raw LWPs, which suffices in the present model. > 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. -- Daniel Jacobowitz Carnegie Mellon University MontaVista Software Debian GNU/Linux Developer