shared library support hookin the remote.c

Kevin Buettner
Mon Jun 28 21:44:00 GMT 2004

On Wed, 23 Jun 2004 18:55:40 -0700
Stephen & Linda Smith <> wrote:

> I have been trying to decide how to hook the solib support into the
> remote protocol and think that what is needed is a pointer to a
> function in remote.c.
> Initially the pointer would be initailized to null (zero) and
> wouldn't be used unless the solib supporting code initialized it to
> point to one of target specific functions.  The reason I came up
> with this idea is that the data that is needed by solib would in
> general not be the same between targets.  Also this would keep the
> code that is to handle this extension out of the remote.c file which
> is general in nature. 
> With this resolved I think I can start coding (starting by adding
> this variable to the tree).  It doesn't make much sense to write the
> solib support if I can't get the data out of the remote target.
> What do you think

I think we need more detail.  Which functions in remote.c would
be affected?   What would the interface look like and how would
it be used?

Also, please note that I am not the maintainer of remote.c...


More information about the Gdb mailing list