https://bugs.kde.org/show_bug.cgi?id=475634
Fred M changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution|---
https://bugs.kde.org/show_bug.cgi?id=475634
--- Comment #4 from Paul Floyd ---
Can this be closed now?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=475634
--- Comment #3 from Fred M ---
Maybe, I found the root cause,
After the
vagrind &
I do a "sleep"
https://bugs.busybox.net/show_bug.cgi?id=15619
Bug 15631 - sleep command after '&' in a shell script has no effect
The sleep is not executed.
I am
https://bugs.kde.org/show_bug.cgi?id=475634
--- Comment #2 from Paul Floyd ---
Also does it work with the simplest tool, "--tool=none"?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=475634
--- Comment #1 from Paul Floyd ---
Try removing the vgdb options. Valgrind will be stopped waiting for a vgdb
connection via named pipe.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=475634
Paul Floyd changed:
What|Removed |Added
Summary|valgrind is no starting |valgrind is not starting
CC|
