gccgo has issues when page size is not 4kB
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gcc |
Fix Released
|
Medium
|
|||
gcc-4.9 (Ubuntu) |
Fix Released
|
Medium
|
Unassigned | ||
Trusty |
Invalid
|
Undecided
|
Unassigned | ||
Utopic |
Fix Released
|
Medium
|
Unassigned | ||
gccgo-4.9 (Ubuntu) |
Invalid
|
Medium
|
Unassigned | ||
Trusty |
Fix Released
|
High
|
Matthias Klose | ||
Utopic |
Invalid
|
Medium
|
Unassigned |
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-
killed by SEGV signal
[18519.673651] init: juju-agent-
In powerpc/
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.
Changed in gcc: | |
importance: | Unknown → Medium |
status: | Unknown → New |
summary: |
- gccgo on ppc64el using split stacks when not supported + gccgo has issues when page size is not 4kB |
Changed in gcc-4.9 (Ubuntu Trusty): | |
status: | New → Invalid |
Changed in gccgo-4.9 (Ubuntu Trusty): | |
importance: | Undecided → Medium |
milestone: | none → trusty-updates |
status: | New → Confirmed |
Changed in gccgo-4.9 (Ubuntu Utopic): | |
status: | Confirmed → Invalid |
Changed in gcc-4.9 (Ubuntu Utopic): | |
importance: | Undecided → Medium |
status: | New → Confirmed |
Changed in gcc: | |
status: | New → Fix Released |
This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:
apport-collect 1304754
and then change the status of the bug to 'Confirmed'.
If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.
This change has been made by an automated script, maintained by the Ubuntu Kernel Team.