touch-packages team mailing list archive
-
touch-packages team
-
Mailing list archive
-
Message #02159
[Bug 1304754] Re: gccgo has issues when page size is not 4kB
I tried the package that Matthias left on the link in the last comment
(1.18.1). I received a similar but different error:
goroutine 3 [syscall]:
goroutine in C code;
stack unavailable
goroutine 10 [IO wait]:
code.google.com_p_go.net_websocket.ReadByte.N57_code.google.c
om_p_go.net_websocket.hybiFrameReaderFactory
/build/buildd/juju-core-1.18.1/src/code.google.com/p/go.net/websocket/hybi.go:113
code.google.com_p_go.net_websocket.NewFrameReader.N57_code.google.com_p_go.net_websocket.hybiFrameReaderFactory
/build/buildd/juju-core-1.18.1/src/code.google.com/p/go.net/websocket/hybi.go:126
code.google.com_p_go.net_websocket.Receive.N40_code.google.com_p_go.net_websocket.Codec
/build/buildd/juju-core-1.18.1/src/code.google.com/p/go.net/websocket/websocket.go:314
launchpad.net_juju_core_rpc_jsoncodec.Receive.N48_launchpad.net_juju_core_rpc_jsoncodec.wsJSONConn
/build/buildd/juju-core-1.18.1/src/launchpad.net/juju-core/rpc/jsoncodec/conn.go:25
launchpad.net_juju_core_rpc_jsoncodec.ReadHeader.pN43_launchpad.net_juju_core_rpc_jsoncodec.Codec
/build/buildd/juju-core-1.18.1/src/launchpad.net/juju-core/rpc/jsoncodec/codec.go:113
launchpad.net_juju_core_rpc.loop.pN32_launchpad.net_juju_core_rpc.Conn
/build/buildd/juju-core-1.18.1/src/launchpad.net/juju-core/rpc/server.go:344
launchpad.net_juju_core_rpc.input.pN32_launchpad.net_juju_core_rpc.Conn
/build/buildd/juju-core-1.18.1/src/launchpad.net/juju-core/rpc/server.go:317
created by launchpad.net_juju_core_rpc.Start.pN32_launchpad.net_juju_core_rpc.Conn
/build/buildd/juju-core-1.18.1/src/launchpad.net/juju-core/rpc/server.go:200
ubuntu@stilson-01:~$
ubuntu@stilson-01:~$ uname -a
Linux stilson-01 3.13.0-32-generic #57-Ubuntu SMP Tue Jul 15 03:50:31 UTC 2014 ppc64le ppc64le ppc64le GNU/Linux
ubuntu@stilson-01:~$ dpkg -l | grep juju
ii juju 1.18.1-0ubuntu1.1 all next generation service orchestration system
ii juju-core 1.18.1-0ubuntu1.1 ppc64el Juju is devops distilled - client
ii juju-deployer 0.3.6-0ubuntu2 all Deploy complex stacks of services using Juju
ii juju-jitsu 0.20-1 all external tools to enhance juju
ii juju-local 1.18.1-0ubuntu1.1 all dependency package for the Juju local provider
ii juju-mongodb 2.4.9-0ubuntu3 ppc64el MongoDB object/document-oriented database for Juju
ii juju-quickstart 1.4.1+bzr88+ppa25~ubuntu14.04.1 all Easy configuration of Juju environments
ii python-jujuclient 0.17.5-0ubuntu2 all Python API client for juju
ubuntu@stilson-01:~$ getconf PAGE_SIZE
65536
The dmesg output looks different will attach that as well.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gccgo-4.9 in Ubuntu.
https://bugs.launchpad.net/bugs/1304754
Title:
gccgo has issues when page size is not 4kB
Status in The GNU Compiler Collection:
Fix Released
Status in “gcc-4.9” package in Ubuntu:
Fix Released
Status in “gccgo-4.9” package in Ubuntu:
Invalid
Status in “gcc-4.9” source package in Trusty:
Invalid
Status in “gccgo-4.9” source package in Trusty:
In Progress
Status in “gcc-4.9” source package in Utopic:
Fix Released
Status in “gccgo-4.9” source package in Utopic:
Invalid
Bug description:
On kernels 3.13-18 and 3.13-23 (there may be others) the kernel is
killing gccgo compiled binaries
[18519.444748] jujud[19277]: bad frame in setup_rt_frame:
0000000000000000 nip 0000000000000000 lr 0000000000000000
[18519.673632] init: juju-agent-ubuntu-local main process (19220)
killed by SEGV signal
[18519.673651] init: juju-agent-ubuntu-local main process ended, respawning
In powerpc/kernel/signal_64.c:
sys_rt_sigreturn is jumping to the badframe: label and executing an
unconditional force_sigsegv which is delivered to the userland
process. Like C++, gccgo tries to decode SIGSEGV as a nil pointer
access and blame some random function that happened to be the top
stack frame.
Reverting to the 3.13-08 kernel appears to resolve the issue which
(weakly) points the finger at the recent switch to 64k pages.
To manage notifications about this bug go to:
https://bugs.launchpad.net/gcc/+bug/1304754/+subscriptions