[Bug 1454183] Re: gccgo crash on powerpc
Launchpad Bug Tracker
1454183 at bugs.launchpad.net
Wed Jun 3 22:01:04 UTC 2015
This bug was fixed in the package gcc-5 - 5.1.1-9ubuntu2
---------------
gcc-5 (5.1.1-9ubuntu2) wily; urgency=medium
* Merge with Debian; remaining changes:
- Build from upstream sources.
gcc-5 (5.1.1-9) unstable; urgency=medium
* Update to SVN 20150602 (r224029, 5.1.1) from the gcc-5-branch.
* Remove byte-compiled libstdc++ pretty printer files on upgrade.
Closes: #785939.
* Fix dangling libgccjit.so symlink.
* Fix base dependency for rtlibs stage builds.
* Fix build failure of the hppa64 cross compiler, introduced by the
gnat cross patches. Closes: #786692.
* Update README.source (Michael Vogt).
* libgo: syscall.Sendfile(): Apply proposed patch for PR go/66378.
(Michael Vogt). LP: #1460530.
* Set CC and CXX matching the same GCC version for the stage1 build.
* Work around PR go/66368, build libgo with -fno-stack-protector.
LP: #1454183.
-- Matthias Klose <doko at ubuntu.com> Wed, 03 Jun 2015 01:02:23 +0200
** Changed in: gcc-5 (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to gcc-5 in Ubuntu.
https://bugs.launchpad.net/bugs/1454183
Title:
gccgo crash on powerpc
Status in The GNU Compiler Collection:
Unknown
Status in docker.io package in Ubuntu:
Invalid
Status in gcc-5 package in Ubuntu:
Fix Released
Bug description:
I see panics of the form below in https://launchpad.net/~snappy-
dev/+archive/ubuntu/image/+build/7403985 and
https://launchpad.net/ubuntu/+source/docker.io/1.6.0+dfsg1-1ubuntu1/+build/7397683
causing FTBFS for snappy and docker.io on powerpc. As these have
separate Go codebases I assume this is a compiler bug?
dh_auto_build -a -O--buildsystem=golang -O--fail-missing
fatal error: unexpected signal during runtime execution
[signal 0xb code=0x1 addr=0x3]
goroutine 16 [running]:
runtime_dopanic
../../../src/libgo/runtime/panic.c:131
runtime_throw
../../../src/libgo/runtime/panic.c:193
sig_panic_leadin
../../../src/libgo/runtime/go-signal.c:247
sig_panic_info_handler
../../../src/libgo/runtime/go-signal.c:281
:0
__go_go
../../../src/libgo/runtime/proc.c:2328
runtime_main
../../../src/libgo/runtime/proc.c:598
goroutine 0 [idle]:
panic during panic
goroutine 0 [idle]:
runtime_dopanic
../../../src/libgo/runtime/panic.c:131
runtime_startpanic
../../../src/libgo/runtime/panic.c:100
runtime_throw
../../../src/libgo/runtime/panic.c:191
runtime_gogo
../../../src/libgo/runtime/proc.c:251
runtime_tracebackothers
../../../src/libgo/runtime/proc.c:767
runtime_dopanic
../../../src/libgo/runtime/panic.c:139
runtime_throw
../../../src/libgo/runtime/panic.c:193
sig_panic_leadin
../../../src/libgo/runtime/go-signal.c:247
sig_panic_info_handler
../../../src/libgo/runtime/go-signal.c:281
:0
__go_go
../../../src/libgo/runtime/proc.c:2328
runtime_main
../../../src/libgo/runtime/proc.c:598
fatal error: unexpected signal during runtime execution
[signal 0xb code=0x1 addr=0x3]
goroutine 16 [running]:
runtime_dopanic
../../../src/libgo/runtime/panic.c:131
runtime_throw
../../../src/libgo/runtime/panic.c:193
sig_panic_leadin
../../../src/libgo/runtime/go-signal.c:247
sig_panic_info_handler
../../../src/libgo/runtime/go-signal.c:281
:0
__go_go
../../../src/libgo/runtime/proc.c:2328
runtime_main
../../../src/libgo/runtime/proc.c:598
goroutine 0 [idle]:
panic during panic
goroutine 0 [idle]:
runtime_dopanic
../../../src/libgo/runtime/panic.c:131
runtime_startpanic
../../../src/libgo/runtime/panic.c:100
runtime_throw
../../../src/libgo/runtime/panic.c:191
runtime_gogo
../../../src/libgo/runtime/proc.c:251
runtime_tracebackothers
../../../src/libgo/runtime/proc.c:767
runtime_dopanic
../../../src/libgo/runtime/panic.c:139
runtime_throw
../../../src/libgo/runtime/panic.c:193
sig_panic_leadin
../../../src/libgo/runtime/go-signal.c:247
sig_panic_info_handler
../../../src/libgo/runtime/go-signal.c:281
:0
__go_go
../../../src/libgo/runtime/proc.c:2328
runtime_main
../../../src/libgo/runtime/proc.c:598
dh_auto_build: go install -v returned exit code 2
To manage notifications about this bug go to:
https://bugs.launchpad.net/gcc/+bug/1454183/+subscriptions
More information about the foundations-bugs
mailing list