gccgo crash on powerpc
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| | gcc |
Incomplete
|
Medium
|
||
| | docker.io (Ubuntu) |
Medium
|
Unassigned | ||
| | gcc-5 (Ubuntu) |
High
|
Unassigned | ||
Bug Description
I see panics of the form below in https:/
dh_auto_build -a -O--buildsystem
fatal error: unexpected signal during runtime execution
[signal 0xb code=0x1 addr=0x3]
goroutine 16 [running]:
runtime_dopanic
../../
runtime_throw
../../
sig_panic_leadin
../../
sig_panic_
../../
:0
__go_go
../../
runtime_main
../../
goroutine 0 [idle]:
panic during panic
goroutine 0 [idle]:
runtime_dopanic
../../
runtime_startpanic
../../
runtime_throw
../../
runtime_gogo
../../
runtime_
../../
runtime_dopanic
../../
runtime_throw
../../
sig_panic_leadin
../../
sig_panic_
../../
:0
__go_go
../../
runtime_main
../../
fatal error: unexpected signal during runtime execution
[signal 0xb code=0x1 addr=0x3]
goroutine 16 [running]:
runtime_dopanic
../../
runtime_throw
../../
sig_panic_leadin
../../
sig_panic_
../../
:0
__go_go
../../
runtime_main
../../
goroutine 0 [idle]:
panic during panic
goroutine 0 [idle]:
runtime_dopanic
../../
runtime_startpanic
../../
runtime_throw
../../
runtime_gogo
../../
runtime_
../../
runtime_dopanic
../../
runtime_throw
../../
sig_panic_leadin
../../
sig_panic_
../../
:0
__go_go
../../
runtime_main
../../
dh_auto_build: go install -v returned exit code 2
Related branches
| Changed in docker.io (Ubuntu): | |
| status: | New → Triaged |
| importance: | Undecided → Medium |
| Changed in docker.io (Ubuntu): | |
| status: | Triaged → Invalid |
| Adam Conrad (adconrad) wrote : | #2 |
This is not docker-specific. It happens for nuntium as well (see the duped bug). This is definitely a regression from gccgo-5 in vivid.
| Changed in gcc-5 (Ubuntu): | |
| importance: | Undecided → High |
| Matthias Klose (doko) wrote : | #3 |
seen already when calling go version
| Robie Basak (racb) wrote : | #4 |
This also failed for go-md2man: https:/
| Launchpad Janitor (janitor) wrote : | #5 |
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-
LP: #1454183.
-- Matthias Klose <email address hidden> Wed, 03 Jun 2015 01:02:23 +0200
| Changed in gcc-5 (Ubuntu): | |
| status: | Confirmed → Fix Released |
| Changed in gcc: | |
| importance: | Unknown → Medium |
| status: | Unknown → Incomplete |


Status changed to 'Confirmed' because the bug affects multiple users.