[valgrind] [Bug 365273] Invalid write to stack location reported after signal handler runs
https://bugs.kde.org/show_bug.cgi?id=365273 Philippe Waroquiers changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #11 from Philippe Waroquiers --- Thanks for the analysis and the patch, this was a tricky problem. Patch (slightly modified) committed in revision 15902. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 365273] Invalid write to stack location reported after signal handler runs
https://bugs.kde.org/show_bug.cgi?id=365273 --- Comment #10 from earl_c...@yahoo.com --- Created attachment 99972 --> https://bugs.kde.org/attachment.cgi?id=99972&action=edit This is the log of the run with the proposed patch. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 365273] Invalid write to stack location reported after signal handler runs
https://bugs.kde.org/show_bug.cgi?id=365273 --- Comment #9 from earl_c...@yahoo.com --- Created attachment 99971 --> https://bugs.kde.org/attachment.cgi?id=99971&action=edit This is a log of the test run using plain 3.11 -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 365273] Invalid write to stack location reported after signal handler runs
https://bugs.kde.org/show_bug.cgi?id=365273 --- Comment #8 from earl_c...@yahoo.com --- I compiled ran the test program like this: gcc -O0 -o test test.c -lpthread taskset 0x03 valgrind -v -v -v -d -d -d --trace-signals=yes --trace-syscalls=yes ./test Using gcc: Version: 4:4.8.2-1ubuntu6 Using libc: 2.19-0ubuntu6.9 I also discovered that the valgrind diagnostic is not issued if taskset 0x01 is used. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 365273] Invalid write to stack location reported after signal handler runs
https://bugs.kde.org/show_bug.cgi?id=365273 --- Comment #7 from Philippe Waroquiers --- Humph, I mean: Just to be sure to be complete, please also add --trace-syscalls=yes -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 365273] Invalid write to stack location reported after signal handler runs
https://bugs.kde.org/show_bug.cgi?id=365273 --- Comment #6 from Philippe Waroquiers --- Just to be sure to be complete, please also add --trace-signals=yes Thanks -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 365273] Invalid write to stack location reported after signal handler runs
https://bugs.kde.org/show_bug.cgi?id=365273 Philippe Waroquiers changed: What|Removed |Added CC||philippe.waroquiers@skynet. ||be --- Comment #5 from Philippe Waroquiers --- Compiled the program on an x86 debian 8.5 and an amd64 debian 7.9. Tried with several valgrind versions, but could not reproduce any write error. Can you run with the traces -v -v -v -d -d -d --trace-signals=yes and attach the resulting trace. Can you attach the trace both with and without your patch ? Thanks -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 365273] Invalid write to stack location reported after signal handler runs
https://bugs.kde.org/show_bug.cgi?id=365273 --- Comment #4 from earl_c...@yahoo.com --- Created attachment 99960 --> https://bugs.kde.org/attachment.cgi?id=99960&action=edit This is the proposed patch to register the extended stack region when delivering a signal. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 365273] Invalid write to stack location reported after signal handler runs
https://bugs.kde.org/show_bug.cgi?id=365273 earl_c...@yahoo.com changed: What|Removed |Added Attachment #99959|0 |1 is obsolete|| Attachment #99959|1 |0 is patch|| --- Comment #3 from earl_c...@yahoo.com --- Comment on attachment 99959 --> https://bugs.kde.org/attachment.cgi?id=99959 This is the proposed patch to register the extended stack region when delivering a signal. Sorry, I copied this from gmane, and the text is broken. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 365273] Invalid write to stack location reported after signal handler runs
https://bugs.kde.org/show_bug.cgi?id=365273 --- Comment #2 from earl_c...@yahoo.com --- Created attachment 99959 --> https://bugs.kde.org/attachment.cgi?id=99959&action=edit This is the proposed patch to register the extended stack region when delivering a signal. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 365273] Invalid write to stack location reported after signal handler runs
https://bugs.kde.org/show_bug.cgi?id=365273 --- Comment #1 from earl_c...@yahoo.com --- Created attachment 99958 --> https://bugs.kde.org/attachment.cgi?id=99958&action=edit This test program causes memcheck to generate an "Invalid write" warning. The test program was compiled on: Linux bambi 3.13.0-52-generic #86-Ubuntu SMP Mon May 4 04:32:15 UTC 2015 i686 i686 i686 GNU/Linux Distributor ID:LinuxMint Description:Linux Mint 17 Qiana Release:17 Codename:qiana gcc (Ubuntu 4.8.4-2ubuntu1~14.04.3) 4.8.4 Copyright (C) 2013 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. -- You are receiving this mail because: You are watching all bug changes.
