|
From: Vinay C. <vin...@gm...> - 2012-03-08 01:40:29
|
Hi all,
I am in the process of developing a tool that modifies some of the
instructions in program execution. For my tool to work, I need to know what
guest registers are being modified by each guest instruction. I realized
that this information is lost in "pre instrumentation optimisation" phase
of valgrind. However, I overcame this obstacle by changing the flow of
valgrind in main_main.c in VEX/priv/ folder. I modified the code in
main_main.c such that the optimisation phase comes after instrumentation.
The only part of optimisation that stayed prior to instrumentation is the
"flattening" of VEX IR. I am able to run my tool with this modification to
valgrind core on a simple benchmark. But, I would like to know if this is
okay to do. I would appreciate any insights in this regard.
Thanks,
Vinay.
|