[Bug lto/56877] When using LTO and linking statically, coredumps contain unusable stack trace

2020-01-17 Thread pinskia at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=56877 Andrew Pinski changed: What|Removed |Added Status|WAITING |RESOLVED Resolution|---

[Bug lto/56877] When using LTO and linking statically, coredumps contain unusable stack trace

2013-04-08 Thread spatz at psybear dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56877 --- Comment #1 from Dror Levin 2013-04-08 14:54:42 UTC --- Created attachment 29825 --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=29825 Simple program that generates coredump (using assert(0))

[Bug lto/56877] When using LTO and linking statically, coredumps contain unusable stack trace

2013-04-08 Thread rguenth at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56877 Richard Biener changed: What|Removed |Added Status|UNCONFIRMED |WAITING Last reconfirmed|

[Bug lto/56877] When using LTO and linking statically, coredumps contain unusable stack trace

2013-04-08 Thread spatz at psybear dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56877 --- Comment #3 from Dror Levin 2013-04-08 15:36:11 UTC --- Using: - binutils 2.23.2, GNU ld - glibc 2.17 - x86_64, linux 3.8 - Arch linux Anything else that may be relevant?