Bug 9126 - pending breakpoints on stripped executables
Summary: pending breakpoints on stripped executables
Status: RESOLVED FIXED
Alias: None
Product: gdb
Classification: Unclassified
Component: breakpoints (show other bugs)
Version: unknown
: P3 enhancement
Target Milestone: ---
Assignee: Not yet assigned to anyone
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-10-17 22:18 UTC by stanleyg76
Modified: 2009-01-14 16:50 UTC (History)
1 user (show)

See Also:
Host:
Target:
Build:
Last reconfirmed:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description stanleyg76 2005-10-17 22:18:01 UTC
[Converted from Gnats 2021]

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).

Release:
gdb cvs-current

Environment:
linux/x86
Comment 1 stanleyg76 2005-10-17 22:18:01 UTC
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."));
Comment 2 Pedro Alves 2009-01-14 16:50:34 UTC
This is fixed in mainline:

2008-08-20  Pedro Alves  <pedro@codesourcery.com>

        * linespec.c (symtab_from_filename): Also throw NOT_FOUND_ERROR if
        there are no symbols loaded, instead of throwing a generic error.
        (decode_variable): Likewise.

In your case, GDB will now ask you if you want to leave the breakpoint pending.