https://bugs.kde.org/show_bug.cgi?id=458915
Libor Peltan changed:
What|Removed |Added
Status|RESOLVED|VERIFIED
--- Comment #28 from Libor Peltan ---
https://bugs.kde.org/show_bug.cgi?id=458915
Philippe Waroquiers changed:
What|Removed |Added
Resolution|--- |FIXED
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=458915
David Vasek changed:
What|Removed |Added
CC||david.va...@nic.cz
--- Comment #26 from David
https://bugs.kde.org/show_bug.cgi?id=458915
--- Comment #25 from Philippe Waroquiers ---
(In reply to Libor Peltan from comment #24)
> You will probably need to run the test several time until it reproduces. It
> may also happen on some machines that it does never reproduce. For me, it
> easily
https://bugs.kde.org/show_bug.cgi?id=458915
--- Comment #24 from Libor Peltan ---
Hi Philippe,
if you have a mood to try out with Knot DNS, these are the instruction to
reproduce:
1) download Knot DNS sources from https://gitlab.nic.cz/knot/knot-dns . It's OK
to stay at the `master` branch.
2)
https://bugs.kde.org/show_bug.cgi?id=458915
--- Comment #23 from Philippe Waroquiers ---
(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
https://bugs.kde.org/show_bug.cgi?id=458915
--- Comment #22 from Libor Peltan ---
(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
https://bugs.kde.org/show_bug.cgi?id=458915
--- Comment #21 from Philippe Waroquiers ---
(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,
https://bugs.kde.org/show_bug.cgi?id=458915
Libor Peltan changed:
What|Removed |Added
Summary|syscall sometimes returns |syscall sometimes returns
