|
From: Shahriyar A. <sm...@co...> - 2007-10-10 13:18:16
|
Hi, I am interested in porting a tool from Valgrind 2.2.0 to Valgrind 3.3.0/svn. I was wondering what is the best way to go about porting the tool, seeing that there have been a lot of changes in Valgrind since 2.2.0. Thank you, Shahriyar |
|
From: Nicholas N. <nj...@cs...> - 2007-10-10 23:16:07
|
On Wed, 10 Oct 2007, Shahriyar Amini wrote: > I am interested in porting a tool from Valgrind 2.2.0 to Valgrind > 3.3.0/svn. I was wondering what is the best way to go about porting the > tool, seeing that there have been a lot of changes in Valgrind since 2.2.0. First, read VEX/pub/libvex_ir.h carefully. It's the best introduction to the new IR, which is the biggest change between the two versions. You should look at some of the existing tools, esp. lackey, for examples. However, you might want to do the instrumentation changes once you've accounted for the other changes... Second, what was vg_skin.h has been broken up into lots of different .h files. You'll need to deal with that. Some of the function names will have changed, too. Also, if your tool assumed 32-bit platforms, it would be better if it no longer did, so it could be used on 64-bit platforms. What does the tool do? The size of the job will depend greatly on how complex it is. Nick |