From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 24989 invoked by alias); 14 Sep 2006 17:49:14 -0000 Received: (qmail 24979 invoked by uid 22791); 14 Sep 2006 17:49:14 -0000 X-Spam-Check-By: sourceware.org Received: from web55610.mail.re4.yahoo.com (HELO web55610.mail.re4.yahoo.com) (206.190.58.234) by sourceware.org (qpsmtpd/0.31) with SMTP; Thu, 14 Sep 2006 17:49:11 +0000 Received: (qmail 56744 invoked by uid 60001); 14 Sep 2006 17:49:09 -0000 Message-ID: <20060914174909.56742.qmail@web55610.mail.re4.yahoo.com> Received: from [137.65.135.207] by web55610.mail.re4.yahoo.com via HTTP; Thu, 14 Sep 2006 10:49:09 PDT Date: Thu, 14 Sep 2006 17:49:00 -0000 From: Lee Subject: preserving gdb symbols To: gdb@sources.redhat.com In-Reply-To: <20060914151039.GA19945@nevyn.them.org> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit 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/msg00081.txt.bz2 Sorry, one more painful shared library symbol question. When I have a customer's machine core, I can open the core with something like gdb --readnow /usr/bin/myapp core.1234 gdb then reads the binaries to read in the needed symtabs I now have every symbol in memory that I need for what I am doing. 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. This is usually in the order of 60 to 100 shared libraries). We ofcourse are doing this on HPUX, linux (redhat and suse), and solaris. So getting every vendor to change their core format while probably the best option, is not very likely. 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. If not, then we are still stuck with always having to have the exact shared library to read the symbols from. The gnu_debug_link is even worthless as u have to read that out of the actual shared library, its not in the core. 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 ? Lee __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com