https://bugs.kde.org/show_bug.cgi?id=356457
--- Comment #15 from Philippe Waroquiers <philippe.waroqui...@skynet.be> --- (In reply to Joost VandeVondele from comment #14) > Also no luck with --sanity-level=4 > > The fact that it is not reproducible on command is indeed not simplifying > this. I wonder if this could be related to something external to valgrind > triggering this. Yes, this bug is quite mysterious. The only remaining thing to try that I see is to add --vgdb-stop-at=valgrindabexit to the valgrind args you use for your regression tests. Then when the error happens, valgrind will wait for a gdb to connect using gdb+vgdb. You can then examine e.g. which library is being mmap-ed. You might also use gdb to directly attach to valgrind and examine valgrind internals. -- You are receiving this mail because: You are watching all bug changes.
