This is the mail archive of the
gdb-prs@sourceware.org
mailing list for the GDB project.
Re: shlibs/2227: gdb dying on very large shared library
- From: Daniel Jacobowitz <drow at false dot org>
- To: nobody at sources dot redhat dot com
- Cc: gdb-prs at sources dot redhat dot com,
- Date: 13 Feb 2007 01:38:01 -0000
- Subject: Re: shlibs/2227: gdb dying on very large shared library
- Reply-to: Daniel Jacobowitz <drow at false dot org>
The following reply was made to PR shlibs/2227; it has been noted by GNATS.
From: Daniel Jacobowitz <drow@false.org>
To: laurent@oget.net
Cc: gdb-gnats@sources.redhat.com
Subject: Re: shlibs/2227: gdb dying on very large shared library
Date: Mon, 12 Feb 2007 20:34:35 -0500
On Mon, Feb 12, 2007 at 04:21:59PM -0000, laurent@oget.net wrote:
> I have been trying to use gdb to debug an application built with g++ on solaris, which uses a lot of templated code and suffers from a pretty bad case of code bloat. The shared library is 154M and nm finds 195254 entry points in it. Should gdb be able to handle this or are we exceeding some limit there?
It should work fine, though perhaps slowly.
> gdb is able, after some time to load the executable and set break points, but when i attempt to run the application in gdb i get thousands of error messages:
>
> BFD: /export/home/devUser/laurent/src/bin/libxArray.so.1: invalid string offset 6074469 >= 32 for section `'
> BFD: /export/home/devUser/laurent/src/bin/libxArray.so.1: invalid
> string offset 561167 >= 80 for section `.shstrtab'
Can objdump load this file? How about readelf -S?
--
Daniel Jacobowitz
CodeSourcery