From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 22201 invoked by alias); 2 Mar 2003 20:15:25 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 22194 invoked from network); 2 Mar 2003 20:15:24 -0000 Received: from unknown (HELO localhost.redhat.com) (24.157.209.173) by 172.16.49.205 with SMTP; 2 Mar 2003 20:15:24 -0000 Received: from redhat.com (localhost [127.0.0.1]) by localhost.redhat.com (Postfix) with ESMTP id 99E9F2A9C; Sun, 2 Mar 2003 15:17:31 -0500 (EST) Message-ID: <3E6266DB.9020704@redhat.com> Date: Sun, 02 Mar 2003 20:15:00 -0000 From: Andrew Cagney User-Agent: Mozilla/5.0 (X11; U; NetBSD macppc; en-US; rv:1.0.2) Gecko/20030223 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Andrew Cagney Cc: gdb@sources.redhat.com Subject: Re: expected behavior of GNU/Linux gcore and corefiles References: <3E617797.5000704@redhat.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2003-03/txt/msg00033.txt.bz2 Dig dig, this has come up before. Up until this change: > 2002-01-04 Daniel Jacobowitz > > * thread-db.c (thread_db_new_objfile): Do not enable thread_db > for core files. > GDB was barfing when trying to load the thread DB. Looking back through that thread, part of the problem appears to have stemed from GDB thinking that the GNU/Linux core file contained threads instead of LWPs :-( Andrew http://sources.redhat.com/ml/gdb-patches/2002-01/msg00017.html http://sources.redhat.com/ml/gdb-patches/2001-12/msg00345.html