From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 13434 invoked by alias); 14 Dec 2001 04:27:17 -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 13325 invoked from network); 14 Dec 2001 04:25:58 -0000 Received: from unknown (HELO nevyn.them.org) (128.2.145.6) by sources.redhat.com with SMTP; 14 Dec 2001 04:25:58 -0000 Received: from drow by nevyn.them.org with local (Exim 3.33 #1 (Debian)) id 16Ejv3-0005Xo-00; Thu, 13 Dec 2001 23:25:57 -0500 Date: Thu, 13 Dec 2001 20:27:00 -0000 From: Daniel Jacobowitz To: Michael Snyder Cc: gdb-patches@sources.redhat.com Subject: Re: [RFA] Don't use thread_db on corefiles Message-ID: <20011213232557.B20920@nevyn.them.org> Mail-Followup-To: Michael Snyder , gdb-patches@sources.redhat.com References: <20011213114847.A17989@nevyn.them.org> <3C190DDC.B32D6A7B@cygnus.com> <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> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3C19543A.2580D12E@cygnus.com> User-Agent: Mutt/1.3.23i X-SW-Source: 2001-12/txt/msg00379.txt.bz2 On Thu, Dec 13, 2001 at 05:22:02PM -0800, Michael Snyder wrote: > Daniel Jacobowitz wrote: > > > > On Thu, Dec 13, 2001 at 03:43:15PM -0800, Michael Snyder wrote: > > > Good, dumping only the LWPs is the right thing to do, I think. > > > But if that's what you're doing, then the thread-db module should > > > still be useful to you: I know it is on Solaris, which this one > > > was modelled after. You'll need it if-and-when the thread-to-lwp > > > mapping ever becomes many-to-one (which may be soon). > > > > See my comments about cross core debugging in my message to Andrew. > > 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. > Not necessarily -- but it's not a decision for one person to make, > while no one else has access to the problem. Right now you're > the only one with access to these new multi-threaded corefiles. > Are the rest of us going to be seeing them soon? We might want > to take part in deciding how best to support them. Hopefully, you'll be seeing them soon :) I'll be publicly submitting the patch if I find a less gross way to do it, and I'm trying. -- Daniel Jacobowitz Carnegie Mellon University MontaVista Software Debian GNU/Linux Developer