On September 21, 2015 23:16:58 Tyson Whitehead wrote:
> I'll check the make sure, but I'm 99.9% certain the code doesn't use any of
> the valgrind API.
>
> I'm nearly certain its first exposure to valgrind was me running it just
> now to help them track down some memory leak issues.
>
> The c
I'll check the make sure, but I'm 99.9% certain the code doesn't use any of
the valgrind API.
I'm nearly certain its first exposure to valgrind was me running it just
now to help them track down some memory leak issues.
The client request in coming from the MPI wrapper library that ships with
val
On 21/09/15 23:04, Tyson Whitehead wrote:
> ==32704== Unaddressable byte(s) found during client check request
> ...
> ==32704== Address 0x243e6040 is 16,384 bytes inside a block of size
> 1,048,576 alloc'd
> ...
>
> and
>
> ==32704== Invalid read of size 8
> ...
> ==32704== Address 0x22fe2040 i
> I've been working on debugging someone else's MPI code and am getting error
> messages that seem pretty strange to me
>
> ==32704== Memcheck, a memory error detector
> ==32704== Copyright (C) 2002-2013, and GNU GPL'd, by Julian Seward et al.
> ==32704== Using Valgrind-3.10.1 and LibVEX; rerun wi
