This is the mail archive of the
mailing list for the GDB project.
Re: GDB and shared libraries
> Or (more likely) it's possible that the OS provides some other
> interface for getting at this information. Again, the two things you
> need are 1) some way to be notified that the dynamic linker has loaded
> (or unloaded) one of the shared libraries and 2) some way to get the
> names of the libraries, their load addresses, and perhaps other
> assorted information. You'll need to consult the docs for your
> proprietary OS and figure out what these mechanisms are. It's quite
> possible that they've provided you with a debugging API for getting at
> this information.
Well, since we wrote the OS and the gdbserver, I think that is doable.
> Anyway, once you've figured out these details, you'll still need to
> put a shared library backend on your target. Fortunately, if you make
> the target stub (gdb server) do most of the work, it ought to be
> pretty simple. I think the generally accepted mechanism for gdb to
> request this kind of target/stub-specific information is the "q"
> packet. GDB's remote protocol is documented at
> At this point, I'll let others jump in because my experience with the
> remote protocol is actually rather limited...
Thanks for pointing me to the doc