From mboxrd@z Thu Jan  1 00:00:00 1970
From: Andrew Cagney <ac131313@cygnus.com>
To: Stephen Smith <ischis2@home.com>
Cc: GDB <gdb@sourceware.cygnus.com>
Subject: Re: GDB and shared libraries
Date: Tue, 27 Feb 2001 08:14:00 -0000
Message-id: <3A9BD1C8.B1C6DDB1@cygnus.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>
X-SW-Source: 2001-02/msg00411.html

> 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