Re: [Valgrind-users] VEX temporary storage exhausted

[Yuri D'E. <wa...@th...>]

On Tue, Mar 19 2019, Philippe Waroquiers wrote:
>> ==19253==    by 0x580A524B: ??? (in /usr/lib/x86_64-linux-gnu/valgrind/memcheck-amd64-linux)
>> ==19253==    by 0x580A71EF: ??? (in /usr/lib/x86_64-linux-gnu/valgrind/memcheck-amd64-linux)
>> ==19253==    by 0x580F5D80: ??? (in /usr/lib/x86_64-linux-gnu/valgrind/memcheck-amd64-linux)
> A 'classically' installed valgrind will give file and linenr in the host backtrace/

I don't have valgrind debugging symbols currently installed.

> The easiest is to increase the constants significantly (e.g. * 10)
> and recompile/retest.  If after that it works, then it would be nice to
> understand why your application needs so much temporary space.
> (and maybe have an idea of really how much your app needs).

Could this buffer be made tunable in the future?
I so far always used a pre-compiled version of valgrind.

> If that does not solve the problem, then I guess a small reproducer will
> help to investigate ...

This is not something I wrote, although there's a double-free I wanted
to investigate. It's also not a small program, linking with quite a few
large libraries.

But it's all fully OSS. I could provide the binaries or a VM with the
executable pre-loaded if somebody is interested in having a look.