From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 2813 invoked by alias); 14 Dec 2001 01:31:15 -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 2400 invoked from network); 14 Dec 2001 01:29:55 -0000 Received: from unknown (HELO cygnus.com) (205.180.230.5) by sources.redhat.com with SMTP; 14 Dec 2001 01:29:55 -0000 Received: from cygnus.com (reddwarf.cygnus.com [205.180.231.12]) by runyon.cygnus.com (8.8.7-cygnus/8.8.7) with ESMTP id RAA19893; Thu, 13 Dec 2001 17:29:53 -0800 (PST) Message-ID: <3C195557.92B1C986@cygnus.com> Date: Thu, 13 Dec 2001 17:31:00 -0000 From: Michael Snyder Organization: Red Hat, Inc. X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.4.2-2smp i686) X-Accept-Language: en MIME-Version: 1.0 To: Daniel Jacobowitz CC: gdb-patches@sources.redhat.com Subject: Re: [RFA] Don't use thread_db on corefiles 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> <20011213190500.A13544@nevyn.them.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-SW-Source: 2001-12/txt/msg00377.txt.bz2 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? 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.