Re: [Dpcl-develop] Some DPCL questions

[James W. <ja...@cs...>]

> 3) I don't think you can do what you want, i.e. calling sleep() with DPCL.
> The problem is that DPCL only knows about functions within the target
> executable. It has no knowledge of functions in any shared libraries. We

This is one area where the hybrid should be different from pure IBM-DPCL
in that MD-Dyninst treats all shared libraries as modules and allows
constituent functions to be called just as any other function in the
executable.

One thing to try would be to insert a call to nanosleep() instead of
sleep().  At least on x86-linux, this promises to not affect any signals.
There is unfortunately some additional complexity since the arg to
nanosleep() is (struct timespec *).  The easiest way to insert such a call
would probably be to have the call to nanosleep() in a probe module,
which can be inserted into the target program and called via ProbeExp.

Not sure yet about the weak symbol problems, but, for the hybrid's
purposes, any function that can be seen by MD-Dyninst should be exported
through the DPCL API.

-J