https://bugs.kde.org/show_bug.cgi?id=356457
Philippe Waroquiers <philippe.waroqui...@skynet.be> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |philippe.waroquiers@skynet.
| |be
--- Comment #1 from Philippe Waroquiers <philippe.waroqui...@skynet.be> ---
The Assertion 'blockSane(a, b)' failed. might indicate that there is a bug in
Valgrind
(buffer overrun in reading the debug information of an mmaped library?).
However, without a small reproducer and/or more details, it is unlikely much
can be done.
Here are a few things you could try, easiest things are first :). If this is a
buffer overrun
in Valgrind, the 2nd action is most likely to find the problem.
* run with -v -v -v -d -d -d and see which library load is loaded just before
the corruption
This might give a hint about how to reproduce the problem and make a small
test case.
* recompile valgrind after having uncommented
// #define DEBUG_MALLOC
in m_mallocfree.c and rerun your test case.
* compile valgrind as an 'inner valgrind', and then run
valgrind <your test case> under valgrind
(see section self-hosting in README_DEVELOPERS ).
This might detect buffer overrun in valgrind heap allocated blocks.
* run with --vgdb-stop-at=valgrindabexit
till the problem reproduces. You can then attach with gdb, and debug
valgrind itself.
(but that will not be easy, and moreover that will be after the corruption
has happened)
--
You are receiving this mail because:
You are watching all bug changes.
