[valgrind] [Bug 419562] PR_SET_PTRACER error with Ubuntu on WSL
https://bugs.kde.org/show_bug.cgi?id=419562 Tom Hughes changed: What|Removed |Added CC||lean...@21csw.com --- Comment #4 from Tom Hughes --- *** Bug 443426 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 419562] PR_SET_PTRACER error with Ubuntu on WSL
https://bugs.kde.org/show_bug.cgi?id=419562 --- Comment #3 from Philippe Waroquiers --- (In reply to Evan Hunter from comment #2) > Thanks for the pointers on testing it on vgdb. > It looks like it still hangs vgdb :-( > I too am not sure what the prctl(PR_SET_PTRACER, 1, 0, 0, 0) call is trying > to achieve. It seems to succeed but still leaves vgdb blocked. Using the debug options -d -d -d of vgdb and -v -v -v -d -d -d of valgrind, it should be possible to have an idea about what does not work. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 419562] PR_SET_PTRACER error with Ubuntu on WSL
https://bugs.kde.org/show_bug.cgi?id=419562 --- Comment #2 from e...@ozhiker.com --- Thanks for the pointers on testing it on vgdb. It looks like it still hangs vgdb :-( I too am not sure what the prctl(PR_SET_PTRACER, 1, 0, 0, 0) call is trying to achieve. It seems to succeed but still leaves vgdb blocked. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 419562] PR_SET_PTRACER error with Ubuntu on WSL
https://bugs.kde.org/show_bug.cgi?id=419562 Philippe Waroquiers changed: What|Removed |Added CC||philippe.waroquiers@skynet. ||be --- Comment #1 from Philippe Waroquiers --- Thanks for the proposed patch. I do not remember the reason for the line ret = VG_(prctl) (PR_SET_PTRACER, 1, 0, 0, 0); prctl PR_SET_PTRACER documentation indicates that the second argument is either PR_SET_PTRACER_ANY (to allow any process to ptrace the caller), or a pid (to allow pid to ptrace the caller) or 0 (to not allow anymore a process to ptrace the caller). So, the reason of the call with the pid 1 is not clear (anymore to me. I must have had a good reason at a time, but not commented :(. That being said: Does calling set_ptracer with value 1 effectively allow vgdb to get a blocked valgrind process out of the syscall ? In other words, before your patch: valgrind sleep 100 in another window: vgdb help and vgdb should block or give error msg or similar (you might use vgdb -d -d -d -d help to get more info about what is going on) and after your patch, vgdb -d -d -d -d help should be able to wake up valgrind and produce the help text. -- You are receiving this mail because: You are watching all bug changes.
