https://bugs.kde.org/show_bug.cgi?id=511717
--- Comment #7 from Libor Peltan <[email protected]> --- Great question! I found out the what happens is that vgdb is attached to the running Valgrind process. (This is done by a script whenever something goes wrong with the application, unrelated to this issue.) In fact, the issue appears when multiple instances of vgdb are attaching to the Valgrind process. Do you think it is possible that the crash appears when one vgdb instance is trying to connect, while another one is already reading out the (large) backtrace? -- You are receiving this mail because: You are watching all bug changes.
