gccgo crash on powerpc

Bug #1454183 reported by Robie Basak on 2015-05-12
28
This bug affects 3 people
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://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

Related branches

Robie Basak (racb) on 2015-05-12
Changed in docker.io (Ubuntu):
status: New → Triaged
importance: Undecided → Medium
Adam Conrad (adconrad) on 2015-05-26
Changed in docker.io (Ubuntu):
status: Triaged → Invalid
Launchpad Janitor (janitor) wrote :

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

Changed in gcc-5 (Ubuntu):
status: New → Confirmed
Adam Conrad (adconrad) wrote :

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 :

seen already when calling go version

Launchpad Janitor (janitor) wrote :

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 <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
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.