shared library support hookin the remote.c

Stephen & Linda Smith
2004-06-24T01:55:40Z

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