From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 13027 invoked by alias); 14 Dec 2001 04:23:58 -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 12871 invoked from network); 14 Dec 2001 04:22:38 -0000 Received: from unknown (HELO nevyn.them.org) (128.2.145.6) by sources.redhat.com with SMTP; 14 Dec 2001 04:22:38 -0000 Received: from drow by nevyn.them.org with local (Exim 3.33 #1 (Debian)) id 16Ejrr-0005VL-00; Thu, 13 Dec 2001 23:22:39 -0500 Date: Thu, 13 Dec 2001 20:23: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: <20011213232239.A20920@nevyn.them.org> Mail-Followup-To: Michael Snyder , gdb-patches@sources.redhat.com References: <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> <20011213190500.A13544@nevyn.them.org> <3C195557.92B1C986@cygnus.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3C195557.92B1C986@cygnus.com> User-Agent: Mutt/1.3.23i X-SW-Source: 2001-12/txt/msg00378.txt.bz2 On Thu, Dec 13, 2001 at 05:26:47PM -0800, Michael Snyder wrote: > Daniel Jacobowitz wrote: > > > > On Thu, Dec 13, 2001 at 06:56:36PM -0500, Daniel Jacobowitz wrote: > > > Thread_db, as things stand, does not work on core files. Is preventing > > > it from trying, and thus crashing GDB, really such a disruptive > > > suggestion? > > > > OK, that came out a little harsher than I really wanted it. Sorry. > > > > I'd like to apply this patch and then add an entry to TODO about > > how it "should be done". Is that better? > > I'd really like to be able to look at the problem myself. > I have a lot invested in gdb's thread support on Linux, and > I don't have any way to reproduce the problem you're trying > to work around. Could you provide a multi-threaded corefile > with corresponding symbol file for folks to experiment with? I'll do that. A binary is at: http://www.them.org/~drow/mtc.tgz (The core file is a 23MB sparse file because of the unmapped user stacks. Careful where you unpack it.) It'll be a couple of days before I can post the patch, at best; I'm trying to sort out stopping threads right now. This patch is based on something posted to linux-kernel several times over the past year by different people; most recent (if my bad memory serves me well) was by Elan Feingold. His patch had a fatal bug, but still produced working core files. > If we agree to have your workaround checked in, and then later > decide that you've solved the problem the wrong way, then it will > be more painful to take out your workaround and make you revisit > the problem (after the bits have been flushed from your mental cache). > Better we all agree on how to solve it first. Sure. But I have a fixed, very imminent deadline on this; the kernel patch took up most of the time. I'll try to spend time on a proper solution later. -- Daniel Jacobowitz Carnegie Mellon University MontaVista Software Debian GNU/Linux Developer