Re: [Valgrind-users] VEX temporary storage exhausted

[Philippe W. <phi...@sk...>]

On Thu, 2019-03-21 at 23:30 +0100, Yuri D'Elia wrote:
> On Thu, Mar 21 2019, Philippe Waroquiers wrote:
> > Strange.
> > The only thing I see that can cause this failure is VexTransOutputFull.
> > 
> > So, the next trial is to bump x10
> > m_translate.c N_TMPBUF
> > 
> > You have to edit similarly the 60000 in VG_(add_to_transtab)
> 
> This seems to have worked.
> 
> What now, though?
Humph, so functionally, valgrind seems to work, but needs an unexpectedly
big amount of memory to handle some piece of code.

The best is to file a bug on bugzilla, attaching more information.
My knowledge in this area is relatively limited, but I think that
the below should give the needed info:

Use the unpatched valgrind (so as to reproduce the problem/crash).
run a first time:
  valgrind --trace-flags=11111111 <yourprogram>

This will output a bunch of lines such as:
...
==== SB 1789 (evchecks 8650) [tid 1] 0x4f833a7 free_mem+231 UNKNOWN_OBJECT+0x0
==== SB 1790 (evchecks 8651) [tid 1] 0x4f832ae free_slotinfo+110 UNKNOWN_OBJECT+0x0
...

Then rerun with
valgrind --trace-flags=11111111 --trace-notbelow=XXXXX <yourprogram>
where XXXXX is one or two numbers before the SB that causes the crash.

File a bug on bugzilla, attaching the resulting trace, and
add the relevant details, such as indicating that increasing the 2 constants
bypasses the problem.

thanks

Philippe