Hi,
I couldn't reproduce this issue, but running marble with helgrind is a
nightmare.
The recommended way use helgrind with kde programs is:
QT_NO_GLIB=1 valgrind --tool=helgrind --track-lockorders=no marble
I find quite useful to have a gdb attached to valgrind with the vgdb
interface, so:
QT_NO_GLIB=1 valgrind --tool=helgrind --track-lockorders=no --vgdb-error=0 --verbose marble
and follow the valgrind indications to have a gdb connected to it.
The backtrace reported upstream seems to have segfaulted after accessing the
value() of a KBiAssociativeContainer right (KMap) result, so, is that an
indication that the map node is no longer valid? I don't know.
Happy hacking,