On Sun, Jun 13, 2010 at 1:51 PM, Robert Berger
wrote:
> On 06/10/2010 07:38 PM, Bart Van Assche wrote:
> I'm using ELDK 4.2 on an AMCC kilauea board:
>
> All on the host:
>
> svn co svn://svn.valgrind.org/valgrind/branches/VALGRIND_3_5_BRANCH
>
> VALGRIND_PATH="VALGRIND_3_5_BRANCH"
>
> The patches
On 06/10/2010 07:38 PM, Bart Van Assche wrote:
Hi,
I'm using ELDK 4.2 on an AMCC kilauea board:
All on the host:
svn co svn://svn.valgrind.org/valgrind/branches/VALGRIND_3_5_BRANCH
VALGRIND_PATH="VALGRIND_3_5_BRANCH"
The patches are attached as well.
This patch is to remove the altivec instru
Hi all,
I'm also posting to the valgrind folks in case any of you have some
idea what's going on. (Please Cc, I'm not subscribed there.) I'm
still not sure who to blame, but at this point, any sort of input
would be *great*. I put some extra comments for non-gitters in
footnotes.
This bug has
On Sun, Jun 13, 2010 at 11:47 AM, Satya V. Gupta wrote:
> I have a supervisory process that is kicked off by an ELF executable which
> in turn invokes some ELF/ python script/ executables based child processes.
> I wish to run valgrind with --tool=callgrind and be able to inject valgrind
> into al
I have a supervisory process that is kicked off by an ELF executable which
in turn invokes some ELF/ python script/ executables based child processes.
I wish to run valgrind with --tool=callgrind and be able to inject valgrind
into all processes. So far I have tried to run the supervisory process w
