https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80914
--- Comment #12 from Steven Noonan ---
Oh this is kind of interesting. It runs fine at '-O1 -ggdb3'
$ go.gcc test -o testbin -gccgoflags '-O1 -ggdb3
-Wl,--compress-debug-sections=zlib'
OK: 136 passed
PASS
ok github.com/twstrike/ed448
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80914
--- Comment #11 from Steven Noonan ---
Weird, I wonder why you can't repro it.
I built with this to get a stack trace (I assume -O and -ggdb work properly
when placed here):
$ go.gcc test -o testbin -gccgoflags '-O0 -ggdb3
-Wl,--compress-debug-
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80914
--- Comment #10 from Ian Lance Taylor ---
I can't recreate the problem. I did the same commands in
github.com/twstrike/ed448 and they worked for me.
Using `go test -c -gccgoflags -Wl,--compress-debug-sections=zlib` to generate
an executable, an
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80914
--- Comment #9 from Steven Noonan ---
(In reply to Ian Lance Taylor from comment #8)
> Which version of GCC are you using in comment #7?
Oops, forgot to mention that bit. Built from trunk a few hours ago:
$ go.gcc version
go version go1.9 gccgo
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80914
--- Comment #8 from Ian Lance Taylor ---
Which version of GCC are you using in comment #7?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80914
--- Comment #7 from Steven Noonan ---
With the compressed debug section support added to libbacktrace, gccgo will run
fine when built using a binutils configured with
--enable-compressed-debug-sections=all. However, programs built with that gccgo
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80914
Ian Lance Taylor changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80914
--- Comment #5 from ian at gcc dot gnu.org ---
Author: ian
Date: Tue Oct 10 16:55:04 2017
New Revision: 253594
URL: https://gcc.gnu.org/viewcvs?rev=253594&root=gcc&view=rev
Log:
PR go/80914
* elf.c (SHF_COMPRESSED): Define.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80914
--- Comment #4 from Steven Noonan ---
This bug is still present, but I believe I know what is causing this.
At the time I reported this, I was using a binutils configured with
--enable-compressed-debug-sections=all. The resulting go.gcc binary j
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80914
--- Comment #3 from Steven Noonan ---
This is from a different go.gcc binary, because I've rebuilt several times to
try and troubleshoot. But this one still exhibits the bad behavior. Just in
case, I've uploaded a copy of the binary, the entire '
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80914
--- Comment #2 from Ian Lance Taylor ---
The failure is in libbacktrace. The program crashes because once libbacktrace
fails the first time, the program is trying to use libbacktrace to show a stack
trace of the failure. This leads to an infini
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80914
--- Comment #1 from Steven Noonan ---
Possibly better backtrace from an -O0 -g build of GCC:
Program received signal SIGSEGV, Segmentation fault.
0x7731307e in __generic_morestack (pframe_size=0x77fa3050,
old_stack=0x77fa3070, pa
12 matches
Mail list logo
