I'm also experiencing this bug, in Jaunty AMD64. There's no specific event that triggers the crash - the valgrind log suggests that there might be an element of randomness about the process.
I've attached the output of a `gdb` session and a separate `valgrind` session. I couldn't get the program to actually crash while running valgrind, but the log does show some definite misbehaviour. It's possible that valgrind somehow avoids actually crashing.
I'm also experiencing this bug, in Jaunty AMD64. There's no specific event that triggers the crash - the valgrind log suggests that there might be an element of randomness about the process.
I've attached the output of a `gdb` session and a separate `valgrind` session. I couldn't get the program to actually crash while running valgrind, but the log does show some definite misbehaviour. It's possible that valgrind somehow avoids actually crashing.