https://bugs.kde.org/show_bug.cgi?id=356457
--- Comment #9 from Philippe Waroquiers <philippe.waroqui...@skynet.be> --- (In reply to Joost VandeVondele from comment #8) > I'll try something similar on the other machine, but the failure is not so > easy to trigger, seemingly. ... > There are many more static libraries involved, and all are compiled with > debug info. The binary is also large (~142Mb). According to the guest stacktrace, the corruption happens when mmap-ing a shared lib (so, when valgrind is reading the debug info of this library), so is probably related to the shared lib being loaded. When self-hosting, you will increase the chance to detect a possible buffer overrun by using --core-redzone-size=xxx with xxx being e.g; 100 bytes, or even 1000 bytes (if that does not give an out of memory) on the inner valgrind, -- You are receiving this mail because: You are watching all bug changes.
