[Bug 1461232] [NEW] gocode FTBFS with golang 1.3 and later on powerpc

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

The last two build attempts for gocode have failed on powerpc due to
what appears to be a bug in the golang compiler.

  go build -o gocode formatters.go scope.go config.go rpc.go cursorcontext.go ripper.go gocode.go autocompletefile.go declcache.go os_posix.go server.go client.go utils.go autocompletecontext.go decl.go package.go
  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

(https://launchpad.net/ubuntu/+source/gocode/20150303-1/+build/7390712,
https://launchpad.net/ubuntu/+source/gocode/20150303-2/+build/7480136)

The first of these builds failed with golang-go 2:1.3.3-1ubuntu4, and
the second with the golang-go 2:1.4.2-3ubuntu2 currently in wily-
proposed; so this is not a regression in golang 1.4.

The build before that built successfully with golang-go
2:1.3.3-1ubuntu4, so the problem appears to have been triggered by code
changes in the gocode package rather than by a regression in golang.

** Affects: gcc-5 (Ubuntu)
     Importance: Undecided
         Status: New

-- 
gocode FTBFS with golang 1.3 and later on powerpc
https://bugs.launchpad.net/bugs/1461232
You received this bug notification because you are a member of Ubuntu Foundations Bugs, which is subscribed to gcc-5 in Ubuntu.