On 21/01/10 02:34, Nicholas Nethercote wrote:
> On Wed, Jan 13, 2010 at 7:47 PM, Tom Hughes wrote:
>>> AFAIK, "valgrind" is only a thin wrapper whose job it is to effectively
>>> or exactly LD_PRELOAD a library which intercepts relevant symbols. My
>>> guess is that, for whatever reason, your ins
On Wed, Jan 13, 2010 at 7:47 PM, Tom Hughes wrote:
>> AFAIK, "valgrind" is only a thin wrapper whose job it is to effectively
>> or exactly LD_PRELOAD a library which intercepts relevant symbols. My
>> guess is that, for whatever reason, your install is lacking the shared
>> object which is suppo
On 13/01/10 05:18, tom fogal wrote:
> Zvi Vered writes:
>> When I ran 'valgrind ln -l' I got:
>> valgrind: failed to start tool 'memcheck' for platform 'x86-linux': no
>> such file or directory
>>
>> What can be the reason for such an error ?
>
> AFAIK, "valgrind" is only a thin wrapper whose job
Zvi Vered writes:
> When I ran 'valgrind ln -l' I got:
> valgrind: failed to start tool 'memcheck' for platform 'x86-linux': no
> such file or directory
>
> What can be the reason for such an error ?
AFAIK, "valgrind" is only a thin wrapper whose job it is to effectively
or exactly LD_PRELOAD a
Hi all,
I installed valgrind 3.5.0 on embedded x86 that runs vanilla 2.6.27.35
with busybox utilities.
The toolchain I used was created using crosstool-ng 1.5.2
When I ran 'valgrind ln -l' I got:
valgrind: failed to start tool 'memcheck' for platform 'x86-linux': no
such file or directory
What c
