From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 28584 invoked by alias); 14 Sep 2006 17:53:55 -0000 Received: (qmail 28576 invoked by uid 22791); 14 Sep 2006 17:53:54 -0000 X-Spam-Check-By: sourceware.org Received: from nevyn.them.org (HELO nevyn.them.org) (66.93.172.17) by sourceware.org (qpsmtpd/0.31.1) with ESMTP; Thu, 14 Sep 2006 17:53:52 +0000 Received: from drow by nevyn.them.org with local (Exim 4.54) id 1GNvPK-0006HK-JA; Thu, 14 Sep 2006 13:53:50 -0400 Date: Thu, 14 Sep 2006 17:53:00 -0000 From: Daniel Jacobowitz To: Lee Cc: gdb@sources.redhat.com Subject: Re: preserving gdb symbols Message-ID: <20060914175350.GA24096@nevyn.them.org> Mail-Followup-To: Lee , gdb@sources.redhat.com References: <20060914151039.GA19945@nevyn.them.org> <20060914174909.56742.qmail@web55610.mail.re4.yahoo.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060914174909.56742.qmail@web55610.mail.re4.yahoo.com> User-Agent: Mutt/1.5.13 (2006-08-11) X-IsSubscribed: yes Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2006-09/txt/msg00082.txt.bz2 On Thu, Sep 14, 2006 at 10:49:09AM -0700, Lee wrote: > Currently i have to use a script to read all of the > loaded statements, parse it, and pipe that out and tar > up all of the needed libraries so that I can get > matching binaries for shared libraries and have a > useful core to read. Just try "info shared". It'll work even if you don't have the libraries physically present (well, on most systems). > So my question is first of all is there any way I can > just save all of the symbol information I have in > memory, so that I can reload it when reading the core > on a different machine. No. Save the files instead. > I modified solib_read_symbols. I changed it so that > if you added a switch on gdb's command line then each > time a call was made to solib_read_symbols I then kept > the file. In my case I used the command interface to > exec tar. A person could tack them on the end of the > core file, or create your own package in whatever > format is generally acceptable. Would a solution of > anything like this be acceptable to get back into the > gdb source ? I think you could relatively easily do this as a wrapper script that invoked GDB. We already ship one such (for gcore); if you wanted to add another, I think that would be reasonable. -- Daniel Jacobowitz CodeSourcery