[Bug libgcc/67336] Verify pointers during stack unwind

2018-02-19 Thread egallager at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67336 Eric Gallager changed: What|Removed |Added Keywords||patch CC|

[Bug libgcc/67336] Verify pointers during stack unwind

2017-01-12 Thread tetra2005 at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67336 Yuri Gribov changed: What|Removed |Added CC||tetra2005 at gmail dot com --- Comment #4

[Bug libgcc/67336] Verify pointers during stack unwind

2016-09-12 Thread pinskia at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67336 Andrew Pinski changed: What|Removed |Added Status|UNCONFIRMED |NEW Last reconfirmed|

[Bug libgcc/67336] Verify pointers during stack unwind

2015-08-24 Thread pinskia at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67336 --- Comment #2 from Andrew Pinski --- https://gcc.gnu.org/ml/gcc-patches/2008-01/msg01474.html There might be another thread with a newer version of the patch which uses futex rather than mincore.

[Bug libgcc/67336] Verify pointers during stack unwind

2015-08-24 Thread pinskia at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67336 --- Comment #1 from Andrew Pinski --- I think it might better to use futex than msync.