From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 3875 invoked by alias); 19 Aug 2003 21:36:35 -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 3867 invoked from network); 19 Aug 2003 21:36:34 -0000 Received: from unknown (HELO hotmail.com) (65.54.244.16) by sources.redhat.com with SMTP; 19 Aug 2003 21:36:34 -0000 Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Tue, 19 Aug 2003 14:36:33 -0700 Received: from 213.66.229.14 by bay1-dav44.bay1.hotmail.com with DAV; Tue, 19 Aug 2003 21:36:33 +0000 X-Originating-IP: [213.66.229.14] X-Originating-Email: [loa_gus@hotmail.com] From: "Staffan Gustafsson" To: "'Paul Koning'" Cc: , Subject: RE: debugging core files from other machines with archived symbol files Date: Tue, 19 Aug 2003 21:36:00 -0000 Message-ID: <001b01c36699$f77475e0$9e00a8c0@BULL> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 In-Reply-To: <16194.9924.707536.389637@gargle.gargle.HOWL> X-OriginalArrivalTime: 19 Aug 2003 21:36:33.0329 (UTC) FILETIME=[F59DBA10:01C36699] X-SW-Source: 2003-08/txt/msg00230.txt.bz2 Problem is mostly in the automation area. On windows, we have a simple script that starts the debugger on the core file, maps in the correct symbols and images from a symbol server, the correct version of the source and takes me to the line causing the crash. When debugging a lot of dumps, that's a big saver. The story using redhat/gdb seems much weeker. So while I could create a directory structure similar to what some client has chosen for his/her machine, copy my files to that location, it is a harder to automate, since I have to start gdb on the core file just to find out what that directory structure is. But I guess it can be done. This is however an area where Microsoft has a more streamlined solution, and it wouldn't hurt to have the possibility to look up symbols/images from a server in gdb. Just my $.02 /Staffan > -----Original Message----- > From: Paul Koning [mailto:pkoning@equallogic.com] > Sent: den 19 augusti 2003 15:32 > To: loa_gus@hotmail.com > Cc: drow@mvista.com; gdb@sources.redhat.com > Subject: Re: debugging core files from other machines with > archived symbol files > > > >>>>> "Erik" == Erik Gustafsson writes: > > Erik> Hmm.. Isn't this something you want to be able to do? > Seems to Erik> me that everybody that is shipping software > to customers would Erik> like to be able to debug crash > dumps from customer sites in a Erik> simple way. > > Erik> I'm not sure I understand on what level the problem > is. Is this Erik> a missing feature in GDB or missing > information in the core Erik> file? > > I don't think there is a real issue in practice. Daniel > briefly stated the requirements -- you need to have a file > system subtree somewhere that has the same shape as the > target system tree. That in general isn't a big deal. > > Given that, you simply point gdb to that subtree with > solib-absolute-prefix, and you're good to go. > > For example, suppose your build procedure produces full > (unstripped) binaries in .../targetroot/usr/lib, > .../targetroot/usr/bin, etc. Then this gets the job done: > gdb .../targetroot/usr/bin/brokenapp > (gdb) set solib-absolute-prefix .../targetroot > (gdb) core customercorefile > > GDB will find the relevant file names and the load addresses > from data stored in the corefile. Well, that depends on the > OS; some don't do a particularly good job. For example, you > may discover, as I did, that you can find text sections of > libs but not data sections. > > paul > > > > >