From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 17849 invoked by alias); 6 Aug 2004 18:08:26 -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 17829 invoked from network); 6 Aug 2004 18:08:24 -0000 Received: from unknown (HELO ns1.xcllnt.net) (209.128.86.226) by sourceware.org with SMTP; 6 Aug 2004 18:08:24 -0000 Received: from dhcp50.pn.xcllnt.net (dhcp50.pn.xcllnt.net [192.168.4.250]) by ns1.xcllnt.net (8.12.11/8.12.11) with ESMTP id i76I8CNw013714; Fri, 6 Aug 2004 11:08:12 -0700 (PDT) (envelope-from marcel@piii.pn.xcllnt.net) Received: from dhcp50.pn.xcllnt.net (localhost [127.0.0.1]) by dhcp50.pn.xcllnt.net (8.13.1/8.13.1) with ESMTP id i76I8C83025867; Fri, 6 Aug 2004 11:08:12 -0700 (PDT) (envelope-from marcel@dhcp50.pn.xcllnt.net) Received: (from marcel@localhost) by dhcp50.pn.xcllnt.net (8.13.1/8.13.1/Submit) id i76I8B1B025866; Fri, 6 Aug 2004 11:08:11 -0700 (PDT) (envelope-from marcel) Date: Fri, 06 Aug 2004 18:08:00 -0000 From: Marcel Moolenaar To: Joel Brobecker Cc: Andrew Cagney , "Nathan J. Williams" , gdb-patches@sources.redhat.com Subject: Re: thread ptids when debugging from core file (x86-linux) Message-ID: <20040806180811.GA25829@dhcp50.pn.xcllnt.net> References: <20040806040959.GL1192@gnat.com> <41131998.2030003@gnu.org> <20040806175818.GR1192@gnat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20040806175818.GR1192@gnat.com> User-Agent: Mutt/1.4.2.1i X-SW-Source: 2004-08/txt/msg00158.txt.bz2 On Fri, Aug 06, 2004 at 10:58:18AM -0700, Joel Brobecker wrote: > > >I've always assumed that corelow.c's mapping between .reg sections and > > >threads was intended as a minimal fallback. The module I wrote for > > >NetBSD's threads (which I'll get into shape for the FSF tree Real Soon > > >Now) punts that list and generates its own list of threads from the > > >memory structures of libpthread in the core file, just as it would for > > >a live process. > > > So do you think I'll have to dig into the inferior memory for data used > by the libpthread library to find that information? Is this something > that would be portable across NPTL versions? Supposing we want to go > that route, does anybody know where to find some documentation (or some > code) that exposes the data structures, so I can try digging into them? [not strictly Linux, but more genericly] But how do you map register contents in the various .reg/# sections to the right thread if there's no way to correlate .reg/# sections to light- weight processes? Would this in fact imply that the IDs needs to match? Or am I missing something here? -- Marcel Moolenaar USPA: A-39004 marcel@xcllnt.net