>> I tried a similar test case like yours and it works ok.
>Unfortunately my
>> program is extremely large and complicated. In fact I get
>other errors
>> like "conditional jump depends on uninitialized value" but
>these errors
>> exist in another part of the code entirely.
>
>If the other
> I tried a similar test case like yours and it works ok. Unfortunately my
> program is extremely large and complicated. In fact I get other errors
> like "conditional jump depends on uninitialized value" but these errors
> exist in another part of the code entirely.
If the other errors include
On 06/24/2011 04:25 PM, John Reiser wrote:
>> When the program runs by itself, all the malloc calls are successful.
>> However when I run it with valgrind's memcheck or massif tools (v
>> 3.6.0), a malloc call fails (which is trying to allocate around 6.4 Gb).
> Which Linux distribution, which Linu
It's always a good idea to try a small test case that has "the same" behavior.
-
#include
#include
#include
#define PDE_MAT_SIZE1 4
#define PDE_MAT_SIZE2 4
int main()
{
int *rowptr = malloc((PDE_MAT_SIZE2 + 1) * sizeof(int));
printf("rowptr=%p errno=%d\n", rowptr,
> When the program runs by itself, all the malloc calls are successful.
> However when I run it with valgrind's memcheck or massif tools (v
> 3.6.0), a malloc call fails (which is trying to allocate around 6.4 Gb).
Which Linux distribution, which Linux kernel ("uname -a"), and which
C runtime l
I'm having a very difficult problem getting valgrind to execute a
program which allocates large amounts of memory (> 20 Gb)
When the program runs by itself, all the malloc calls are successful.
However when I run it with valgrind's memcheck or massif tools (v
3.6.0), a malloc call fails (which
