https://bugs.kde.org/show_bug.cgi?id=511717
--- Comment #9 from Libor Peltan <[email protected]> --- I tried to prevent simultaneous access by multiple vgdb to the running Valgrind, now only subseqent (but still multiple) readouts are enabled. In fact, the vgdb is always invoked like this: gdb -ex "set confirm off" -ex "target remote | vgdb -d -d -d -T --pid=<valgrind_pid>" -ex "info threads" -ex "thread apply all bt full" -ex q <knot_dns_binary> The issue is still reproducible in those conditions. What I can see is usually: - in the valgrind output, nothing interesting, just a SIGSEGV reaction - in the gdb stdout, the print of the bactrace is cut half just after some thread header: Thread 4 (Thread 210684 (tid 4 VgTs_WaitSys)): - in the gdb stderr, the message "No registers." appears. Subsequent lines probably belong to subsequent calls of gdb which fail to attach. I'm attaching the most verbose output of valgrind, vgdb (stdout) and vgdb (stderr). Please note that this is appended from multiple (subsequent) runs of (v)gdb. -- You are receiving this mail because: You are watching all bug changes.
