https://bugs.kde.org/show_bug.cgi?id=458915
--- Comment #21 from Philippe Waroquiers <philippe.waroqui...@skynet.be> --- (In reply to Libor Peltan from comment #20) > Thank you for your observations! Based on this, we actually found out that > the issue happens exactly (sometimes!) when we attach vgdb to the running > process, like this: > > ``` > /usr/bin/gdb -ex "set confirm off" -ex "target remote | /usr/bin/vgdb > --pid=5944" -ex "info threads" -ex "thread apply all bt full" -ex q > /home/peltan/master_knot/src/knotd > ``` > > I apologize that we overlooked this improtant fact earlier. (Our test > environment performs this automatically when a routine error occurs.) > > We will continue working on minimizing the reproducer in following days. That starts to clarify where the problem could originate from. Valgrind should stop by itself when it finds an error (when using --vgdb-error argument) and invoke its gdbserver, waiting for gdb/vgdb to connect. Do you mean that the above command is launched (somewhat asynchronously) when an error is detected via other ways ? If yes, as a bypass for this bug, you might try to have valgrind invoking gdbserver and then launch gdb/vgdb, rather than having gdb/vgdb 'interrupting' a (still) running process. But in any case, what you are doing should not cause a problem. When I have a little bit of time, I will dig again in the vgdb logic and see if/where it could create such wrong interaction. -- You are receiving this mail because: You are watching all bug changes.
