[valgrind] [Bug 361615] Inconsistent termination when an instrumented multithreaded process is terminated by signal

https://bugs.kde.org/show_bug.cgi?id=361615 --- Comment #13 from earl_c...@yahoo.com --- Created attachment 101149 --> https://bugs.kde.org/attachment.cgi?id=101149=edit Standalone test case I could not find the previously mentioned standalone test case, so I've uploaded a reconstructed

[valgrind] [Bug 361615] Inconsistent termination when an instrumented multithreaded process is terminated by signal

https://bugs.kde.org/show_bug.cgi?id=361615 --- Comment #12 from Ben Cooksley --- The content of attachment 100145 has been deleted for the following reason: Removing non-relevant content -- You are receiving this mail because: You are watching all bug changes.

[valgrind] [Bug 361615] Inconsistent termination when an instrumented multithreaded process is terminated by signal

https://bugs.kde.org/show_bug.cgi?id=361615 --- Comment #11 from earl_c...@yahoo.com --- (In reply to Ivo Raisr from comment #10) > As Philippe pointed out, there is a problem with the existing attachment. > Please have a look what is there inside and re-attach. Yes, that's obviously wrong. Let

[valgrind] [Bug 361615] Inconsistent termination when an instrumented multithreaded process is terminated by signal

https://bugs.kde.org/show_bug.cgi?id=361615 --- Comment #10 from Ivo Raisr --- As Philippe pointed out, there is a problem with the existing attachment. Please have a look what is there inside and re-attach. -- You are receiving this mail because: You are watching all bug

[valgrind] [Bug 361615] Inconsistent termination when an instrumented multithreaded process is terminated by signal

https://bugs.kde.org/show_bug.cgi?id=361615 --- Comment #9 from earl_c...@yahoo.com --- Comment on attachment 100145 --> https://bugs.kde.org/attachment.cgi?id=100145 Self contained test case . -- You are receiving this mail because: You are watching all bug changes.

[valgrind] [Bug 361615] Inconsistent termination when an instrumented multithreaded process is terminated by signal

https://bugs.kde.org/show_bug.cgi?id=361615 --- Comment #8 from Philippe Waroquiers --- (In reply to earl_chew from comment #4) > Created attachment 100145 [details] > Self contained test case It seems there was an attachment problem. Could you re-attach the self

[valgrind] [Bug 361615] Inconsistent termination when an instrumented multithreaded process is terminated by signal

https://bugs.kde.org/show_bug.cgi?id=361615 --- Comment #7 from Philippe Waroquiers --- (In reply to Julian Seward from comment #6) > Philippe, didn't you fix something like this recently? Not recently. Related to thread termination, I did something some years ago,

[valgrind] [Bug 361615] Inconsistent termination when an instrumented multithreaded process is terminated by signal

https://bugs.kde.org/show_bug.cgi?id=361615 Julian Seward changed: What|Removed |Added CC||philippe.waroquiers@skynet.

[valgrind] [Bug 361615] Inconsistent termination when an instrumented multithreaded process is terminated by signal

https://bugs.kde.org/show_bug.cgi?id=361615 --- Comment #5 from earl_c...@yahoo.com --- I compiled and ran the submitted test case both with and without valgrind. This shows that under valgrind, the child process terminates with SIGKILL rather than the expected SIGTERM. $ gcc -o test test.c

[valgrind] [Bug 361615] Inconsistent termination when an instrumented multithreaded process is terminated by signal

https://bugs.kde.org/show_bug.cgi?id=361615 --- Comment #4 from earl_c...@yahoo.com --- Created attachment 100145 --> https://bugs.kde.org/attachment.cgi?id=100145=edit Self contained test case -- You are receiving this mail because: You are watching all bug changes.

[valgrind] [Bug 361615] Inconsistent termination when an instrumented multithreaded process is terminated by signal

https://bugs.kde.org/show_bug.cgi?id=361615 --- Comment #3 from earl_c...@yahoo.com --- (In reply to Julian Seward from comment #2) > Do you have a small test case which demonstrates that Valgrind's behaviour at > present, differs from when the program is run "natively" ? In the bug description,

[valgrind] [Bug 361615] Inconsistent termination when an instrumented multithreaded process is terminated by signal

https://bugs.kde.org/show_bug.cgi?id=361615 --- Comment #2 from Julian Seward --- Do you have a small test case which demonstrates that Valgrind's behaviour at present, differs from when the program is run "natively" ? I'd be happier about this if you have something directly

[valgrind] [Bug 361615] Inconsistent termination when an instrumented multithreaded process is terminated by signal

https://bugs.kde.org/show_bug.cgi?id=361615 Ivo Raisr changed: What|Removed |Added CC||iv...@ivosh.net -- You are

[valgrind] [Bug 361615] Inconsistent termination when an instrumented multithreaded process is terminated by signal

https://bugs.kde.org/show_bug.cgi?id=361615 --- Comment #1 from earl_c...@yahoo.com --- Created attachment 98326 --> https://bugs.kde.org/attachment.cgi?id=98326=edit Candidate patch to propagate termination signal Here is an attempt to propagate the signal that terminates a thread into the