|
From: Shahriyar A. <sm...@co...> - 2007-10-01 16:41:28
|
Hi everyone, I am in the process of porting a tool that was written in Valgrind 2.2.0 to Valgrind 3.3.0. I have attained my copy of the source code from svn. I was wondering if there is a quick and easy way to save the work under : UCodeBlock* SK_(instrument)(UCodeBlock* cb_in, Addr orig_addr) to the corresponding: IRSB* fb_instrument( VgCallbackClosure* closure, IRSB* bb, VexGuestLayout layout, VexGuestExtents* vge, IRType gWordTy, IRType hWordTy ) I appreciate any feedback. Thank you, Shahriyar |
|
From: Nicholas N. <nj...@cs...> - 2007-10-03 23:34:16
|
On Mon, 1 Oct 2007, Shahriyar Amini wrote: > I am in the process of porting a tool that was written in Valgrind 2.2.0 > to Valgrind 3.3.0. I have attained my copy of the source code from svn. > I was wondering if there is a quick and easy way to save the work under : > > UCodeBlock* SK_(instrument)(UCodeBlock* cb_in, Addr orig_addr) > to the corresponding: > IRSB* fb_instrument( VgCallbackClosure* closure, IRSB* bb, > VexGuestLayout layout, VexGuestExtents* vge, IRType gWordTy, IRType > hWordTy ) I'm not sure what you mean by "save the work under". But I suspect the short answer is "no". The IR change (away from UCode, to Vex IR) was a big change between 2.x and 3.x, and you'll have to rewrite the 'instrument' to account for it. VEX/pub/libvex_ir.h explains how Vex IR works, you might also want to look at 'lackey', the example tool. Nick |