Re: [Valgrind-users] pls help me explaining some valgrind complaints

[Tom H. <to...@co...>]

On 16/03/2019 11:42, Matthias Apitz wrote:
> El día sábado, marzo 16, 2019 a las 09:23:06a. m. +0100, Matthias Apitz escribió:
> 
>>> What is the value of MAX_FSTAB_ROWS ?
>>
>> #define MAX_FSTAB_ROWS 3000
> 
> I set a gdb breakpoint at the entry of FstabInit(). The size of the
> array is:
> 
> (gdb) p sizeof(t_sik_fstab)
> $4 = 950
> (gdb) p sizeof(myFSTABrows)
> $5 = 2850000
> 
> and as well I can not see anything unusual while stepping through the
> init sequence of the function.

That's nearly 3Mbytes that you are creating on the stack
which is quite a lot...

More importantly it is more than the default value that
valgrind uses for --max-stackframe so it is likely to lead
to confusion - do you get a warning about a stack switch
being assumed before those other messages?

Try using --max-stackframe=4000000 or something to specify
a larger maximum stack frame size and see if that helps.

Tom

-- 
Tom Hughes (to...@co...)
http://compton.nu/