[valgrind] [Bug 409367] exit_group() after signal arriving to thread waiting in futex() causes hangs
https://bugs.kde.org/show_bug.cgi?id=409367 --- Comment #6 from Philippe Waroquiers --- (In reply to Allison Karlitskaya from comment #5) > (In reply to Philippe Waroquiers from comment #4) > > Pushed as 63a9f0793 > > Thanks very much, Philippe. > > A few questions, if you don't mind: > > 1) is there any workaround to this problem that you can imagine (in terms of > commandline flags, etc.) that void avoid the problem other than to update > valgrind to a version that includes this patch? Our current workaround is > to add a sleep on the main thread before exit, and I'd like to remove that > ASAP. I do not see a workaround at valgrind command line level. > > 2) when is this patch likely to appear in a release? when is it likely to > appear in a stable release? We only have stable releases :). Typically, there is a release every 6 months or so. The last release was the 12 of April. > > 3) do you think this patch is suitable for backporting/vendor-patching for > distro packages? The patch can for sure be backported, if some distro want to do it. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 409367] exit_group() after signal arriving to thread waiting in futex() causes hangs
https://bugs.kde.org/show_bug.cgi?id=409367 --- Comment #5 from Allison Karlitskaya --- (In reply to Philippe Waroquiers from comment #4) > Pushed as 63a9f0793 Thanks very much, Philippe. A few questions, if you don't mind: 1) is there any workaround to this problem that you can imagine (in terms of commandline flags, etc.) that void avoid the problem other than to update valgrind to a version that includes this patch? Our current workaround is to add a sleep on the main thread before exit, and I'd like to remove that ASAP. 2) when is this patch likely to appear in a release? when is it likely to appear in a stable release? 3) do you think this patch is suitable for backporting/vendor-patching for distro packages? Thanks again. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 409367] exit_group() after signal arriving to thread waiting in futex() causes hangs
https://bugs.kde.org/show_bug.cgi?id=409367 Philippe Waroquiers changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #4 from Philippe Waroquiers --- Pushed as 63a9f0793 -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 409367] exit_group() after signal arriving to thread waiting in futex() causes hangs
https://bugs.kde.org/show_bug.cgi?id=409367 --- Comment #3 from Philippe Waroquiers --- Created attachment 121295 --> https://bugs.kde.org/attachment.cgi?id=121295=edit fix hands and loops when process sends signal to itself I have tested with the reproducer attached, and it works. The test added by the patch is similar to this test. If no remark on the approach, I will push in a few days ... -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 409367] exit_group() after signal arriving to thread waiting in futex() causes hangs
https://bugs.kde.org/show_bug.cgi?id=409367 Philippe Waroquiers changed: What|Removed |Added Assignee|jsew...@acm.org |philippe.waroquiers@skynet. ||be -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 409367] exit_group() after signal arriving to thread waiting in futex() causes hangs
https://bugs.kde.org/show_bug.cgi?id=409367 Philippe Waroquiers changed: What|Removed |Added CC||philippe.waroquiers@skynet. ||be --- Comment #2 from Philippe Waroquiers --- This looks very similar to a loop reproduced with 409141. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 409367] exit_group() after signal arriving to thread waiting in futex() causes hangs
https://bugs.kde.org/show_bug.cgi?id=409367 --- Comment #1 from Allison Karlitskaya --- Forgot to mention: this is against valgrind-3.14.0 as shipped with Ubuntu 19.04. -- You are receiving this mail because: You are watching all bug changes.
