|
From: Jason K. <kra...@ca...> - 2011-03-29 15:25:59
|
On 03/29/2011 10:13 AM, Tom Hughes wrote: > On 29/03/11 15:33, Jason Kraftcheck wrote: > >> Can anyone offer any suggestions about how to use valgrind in an environment >> which doesn't support shared libraries? I could staticly link the valgrind >> components into my program but it isn't clear how to handle initialization, >> startup, etc. The first problem will be the multiple main routines. > > Well valgrind is mostly static - the only place it uses shared libraries > is to inject it's malloc etc replacements into your programs. > > If you really want to do this, it is only the code from the various > vgpreload*.so libraries that you need to link into your program. You > should then still be able to use valgrind in the normal way. > I tried that but I get errors like: valgrind: failed to start tool 'memcheck' for platform 'ppc32-linux': Function not implemented Is there something I can specify for --tool= to tell valgrind not to try to load anything (because I've already statically linked coregrind and memcheck)? thanks, - jason |