https://bugs.kde.org/show_bug.cgi?id=458915
--- Comment #23 from Philippe Waroquiers <philippe.waroqui...@skynet.be> --- (In reply to Libor Peltan from comment #22) > (In reply to Philippe Waroquiers from comment #21) > > Valgrind should stop by itself when it finds an error (when using > > --vgdb-error argument) > > The error mentioned by me is an error in application logic. Valgrind has no > way to detect it, no reason to stop in that case and it does not. > > > 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. > > Yes, we can use a workaround that we don't invoke vgdb at all in such cases. > But in any case, it would be nice to fix what's going wrong in Valgrind. > > > 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. > > Thank you for continuous effor in this issue! I tried to create a tiny small > program that does only listens to incomming UDP packets while using poll or > epoll_wait syscalls, and frequently attach vgdb to it. Unfortunately, the > issue did not reproduce in this simple scenario. You might need to have a mixture of threads executing some cpu instructions, some threads blocked in syscalls, and some signals such as SIGALRM. > The only reproducer we have > so far (at least pretty reliable) is the whole Knot DNS and its test-case. > If you wish, we can give you instructions how to build it and launch the > test-case, but it'll be several steps to do. If the instructions are not too long to describe, it will not harm to have them. If simple enough and building Knot DNS does not need too much dependencies etc ..., I can give it a try. -- You are receiving this mail because: You are watching all bug changes.
