This is the mail archive of the
gdb@sources.redhat.com
mailing list for the GDB project.
Re: GDB and shared libraries
- To: Stephen Smith <ischis2 at home dot com>
- Subject: Re: GDB and shared libraries
- From: Andrew Cagney <ac131313 at cygnus dot com>
- Date: Tue, 27 Feb 2001 11:11:52 -0500
- Cc: GDB <gdb at sourceware dot cygnus dot com>
- References: <3A84136A.23BAF90F@home.com> <1010209182220.ZM4621@localhost.localdomain> <3A845A56.5EF8F61@home.com> <3A9AB471.5F46554@home.com> <1010226205415.ZM30678@localhost.localdomain> <3A9ADDF4.FD998D6E@home.com> <1010226233506.ZM13209@ocotillo.lan> <3A9B0022.16ABBBE0@home.com> <1010227013252.ZM13444@ocotillo.lan> <3A9B35E4.33B1868B@home.com>
> Ok, what do I need to add (commands, data, etc.) to my gdb server to trace into these libraries? Is the spec written
> down?
Just FYI.
Most shared library implementations can, in theory, be debugged remotely
without any modifications to the GDB remote protocol. This is because
the SHLIBs are handled using only memory read/writes and breakpoints.
The ``exercise left to the reader'' is getting what was native-only
SHLIB code re-written in a way that is host independant.
good luck,
Andrew