This is the mail archive of the gdb@sources.redhat.com mailing list for the GDB project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: Shared libraries and the solib interface

From: "Stephen P. Smith" <ischis2 at cox dot net>
To: Kevin Buettner <kevinb at redhat dot com>
Cc: gdb <gdb at sources dot redhat dot com>
Date: Thu, 02 Oct 2003 13:50:41 -0700
Subject: Re: Shared libraries and the solib interface
References: <3F7BA58F.9050803@cox.net> <1031002054312.ZM15015@localhost.localdomain> <3F7BC5AD.9020706@cox.net> <1031002191528.ZM18319@localhost.localdomain>

Kevin Buettner wrote:

And a second question is how does a generic stub inform the GDB (workstation side) app which shared library got loaded and where or is this not necessary?

For svr4- and sunos-like shared library support, this information is available by examining the target's memory.

It is available. I guess I didn't explain well enough.

Given that I know where/what is loaded on the target machine which is running gdbserver, how do I communicate to the workstation running gdb to load the symbol file and the addresses of the various sections?

sps

References:
- Shared libraries and the solib interface
  - From: Stephen & Linda Smith
- Re: Shared libraries and the solib interface
  - From: Kevin Buettner
- Re: Shared libraries and the solib interface
  - From: Stephen & Linda Smith
- Re: Shared libraries and the solib interface
  - From: Kevin Buettner

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]