[Dpcl-develop] Re: dpcl Linux C++ support, C++ limits (Dave Wootton)

[Jaydeep M. <jpm...@un...>]

I am not familiar with the DPCL API, but I use DynInst (www.dyninst.org), a 
standalone instrumentation library, which is descended from the same original 
source as the DPCL instrumentation core.

In DynInst version 3.0 (latest version), you can instrument the target to 
replace/remove function calls, specifically intended to do run-time 
computation steering.

.. AFAIK, DynInst correctly demangles g++ compiled C++ functions, but has 
trouble demangling  xlC compiled C++ progs (on AIX), due to different name 
mangling conventions b/w the compilers.

DynInst has un-documented API calls to get local function variable addresses 
(global vars are straightforward), unfortunately these are returned in terms 
of "offsets from the stack pointer", and there is no API call to get register 
values (the stack pointer) in the instrumentation snippet....but this looks 
hackable from the DynInst source code. (...however, retrieving per Object 
data might be more difficult.)


Regards,
Jaydeep