This is the mail archive of the
gdb-prs@sourceware.org
mailing list for the GDB project.
breakpoints/2021: pending breakpoints on stripped executables
- From: stanleyg76 at yahoo dot com
- To: gdb-gnats at sources dot redhat dot com
- Date: 17 Oct 2005 22:10:04 -0000
- Subject: breakpoints/2021: pending breakpoints on stripped executables
- Reply-to: stanleyg76 at yahoo dot com
>Number: 2021
>Category: breakpoints
>Synopsis: pending breakpoints on stripped executables
>Confidential: no
>Severity: serious
>Priority: medium
>Responsible: unassigned
>State: open
>Class: change-request
>Submitter-Id: net
>Arrival-Date: Mon Oct 17 22:18:01 GMT 2005
>Closed-Date:
>Last-Modified:
>Originator: stanleyg76@yahoo.com
>Release: gdb cvs-current
>Organization:
>Environment:
linux/x86
>Description:
I am trying to debug a shared library which is loaded by
the 'driver' application. The 'driver' application has been
stripped. Attempting to set a pending breakpoint on the
source code in the library fails since the main application
is stripped. A workaround would be to try to set same
breakpoint after some library with debug symbols has been
loaded (this is cumbersome and unfeasible if i am debugging
the application from within Eclipse).
>How-To-Repeat:
>Fix:
linespec.c (in symtab_from_filename function)
comment out the following lines:
if (!have_full_symbols () && !have_partial_symbols ())
error (_("No symbol table is loaded. Use the \"file\" command."));
>Release-Note:
>Audit-Trail:
>Unformatted: