https://bugs.kde.org/show_bug.cgi?id=405782
Bug ID: 405782
Summary: "VEX temporary storage exhausted" when attempting to
debug slic3r-pe
Product: valgrind
Version: 3.14.0
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: memcheck
Assignee: jsew...@acm.org
Reporter: wav...@thregr.org
Target Milestone: ---
SUMMARY
When attempting to run memcheck (valgrind 3.14.0 on debian unstable) on
slic3r-pe (https://github.com/prusa3d/Slic3r/) freshly compiled with gcc 8.3 I
get the following:
> $ valgrind ./src/slic3r-gui
> ==19253== Memcheck, a memory error detector
> ==19253== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al.
> ==19253== Using Valgrind-3.14.0 and LibVEX; rerun with -h for copyright info
> ==19253== Command: ./src/slic3r-gui
> ==19253==
> VEX temporary storage exhausted.
> Pool = TEMP, start 0x59640548 curr 0x59b04c90 end 0x59b05087 (size 5000000)
Under suggestion from Philippe Waroquiers I bumped the following buffers:
- N_TEMPORARY_BYTES 10x
- N_PERMANENT_BYTES 10x
- N_TMPBUF (and related hard-coded size assertions!) 10x
After that, memcheck runs correctly on the executable.
All three buffers had to be increased in order to run memcheck.
Please see the discussion thread on valgrind-users for further details:
https://sourceforge.net/p/valgrind/mailman/message/36617210/
Slic3r is a large program depending on wx 3.1 (also self-compiled). It's not a
program I wrote, I just encountered the problem.
SOFTWARE/OS VERSIONS
Linux 4.19 (debian unstable) on amd64.
--
You are receiving this mail because:
You are watching all bug changes.
