From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 26949 invoked by alias); 2 Mar 2003 20:32: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 26942 invoked from network); 2 Mar 2003 20:32:25 -0000 Received: from unknown (HELO crack.them.org) (65.125.64.184) by 172.16.49.205 with SMTP; 2 Mar 2003 20:32:25 -0000 Received: from nevyn.them.org ([66.93.61.169] ident=mail) by crack.them.org with asmtp (Exim 3.12 #1 (Debian)) id 18pc1Y-0005pQ-00; Sun, 02 Mar 2003 16:33:36 -0600 Received: from drow by nevyn.them.org with local (Exim 3.36 #1 (Debian)) id 18pa8E-0006Uz-00; Sun, 02 Mar 2003 15:32:22 -0500 Date: Sun, 02 Mar 2003 20:32:00 -0000 From: Daniel Jacobowitz To: Andrew Cagney Cc: gdb@sources.redhat.com Subject: Re: expected behavior of GNU/Linux gcore and corefiles Message-ID: <20030302203222.GB24948@nevyn.them.org> Mail-Followup-To: Andrew Cagney , gdb@sources.redhat.com References: <3E617797.5000704@redhat.com> <3E6266DB.9020704@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3E6266DB.9020704@redhat.com> User-Agent: Mutt/1.5.1i X-SW-Source: 2003-03/txt/msg00035.txt.bz2 On Sun, Mar 02, 2003 at 03:17:31PM -0500, Andrew Cagney wrote: > 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 Yep. Among other things the problems arise because thread_db passes requests to lin-lwp instead of properly along the target stack; lin-lwp should be sitting in the "process" slot on the target stack. There are also load/unload issues; observers are the perfect way to fix that. -- Daniel Jacobowitz MontaVista Software Debian GNU/Linux Developer