[Bug 1304754] Re: gccgo has issues when page size is not 4kB

[Dave Cheney]

Hi Matt,

Can you please post the output of dmesg, that is the canonical way to
diagnose this issue atm.

On Thu, Jul 10, 2014 at 5:23 AM, Matt Bruzek
<matthew.bruzek at canonical.com> wrote:
> I installed the debian packages from the CI server http://juju-ci.vapour.ws:8080/job/publish-revision/588/
> My understanding is these deb packages were built with the PPA toolchain that has the fix installed.
>
> I destroyed the environment, rebooted the machine (for good measure) and
> find that I still get an error.
>
> https://pastebin.canonical.com/113210/
>
> Are we sure this fixes the problem?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> 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:
>   Fix Committed
> 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

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to gcc-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:
  Fix Committed
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