|
From: Dmitry K. <kir...@gm...> - 2009-09-03 13:58:51
|
Hello I am trying to transport my tool that worked with valgrind 3.0 to version 3.5.0. I succeeded to compile and execute it, but my internal memory allocation functions are not called and regular malloc in /lib/tls/i686/cmov/libc is called instead. VG_(needs_malloc_replacement) is called and initialises functions. VG_(basic_tool_funcs) and other functions in pre_clo_init are also called and the internal functions that initialised their are also successfully called. Just memory allocation functions (that were initialised in VG_(needs_malloc_replacement)) like malloc, alighn calloc... make problems. I will appreciate very much your help. Thank you Dima |
|
From: Tom H. <to...@co...> - 2009-09-03 14:13:24
|
On 03/09/09 14:52, Dmitry Kirzhner wrote: > I am trying to transport my tool that worked with valgrind 3.0 to > version 3.5.0. I succeeded to compile and execute it, but my internal > memory allocation functions are not called and regular malloc in > /lib/tls/i686/cmov/libc is called instead. > VG_(needs_malloc_replacement) is called and initialises functions. > VG_(basic_tool_funcs) and other functions in pre_clo_init are also > called and the internal functions that initialised their are also > successfully called. Just memory allocation functions (that were > initialised in VG_(needs_malloc_replacement)) like malloc, alighn > calloc... make problems. How can anything in libc get called? Valgrind (deliberately) does not link against libc... Tom -- Tom Hughes (to...@co...) http://www.compton.nu/ |