[Bug 1261604] Re: static binaries compiled with gccgo can fail to set up their address space

[Launchpad Bug Tracker]

This bug was fixed in the package gcc-4.8 - 4.8.2-10ubuntu2

---------------
gcc-4.8 (4.8.2-10ubuntu2) trusty; urgency=low

  * Update to SVN 20131220 (r206145) from the gcc-4_8-branch.
  * Set the goarch to arm64 for aarch64-linux-gnu.
  * Fix statically linked gccgo binaries on AArch64 (Michael Hudson).
    LP: #1261604.
  * Merge accumulated Ada changes from gnat-4.8.
  * Update gnat build dependencies when not built from a separate source.
 -- Matthias Klose <doko at ubuntu.com>   Fri, 20 Dec 2013 18:24:08 +0100

** Changed in: gcc-4.8 (Ubuntu)
       Status: New => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to gcc-4.8 in Ubuntu.
https://bugs.launchpad.net/bugs/1261604

Title:
  static binaries compiled with gccgo can fail to set up their address
  space

Status in “gcc-4.8” package in Ubuntu:
  Fix Released

Bug description:
  As reported in https://code.google.com/p/go/issues/detail?id=6926, a
  static binary produced by gccgo will fail to start up around 60% of
  the time with a message like:

  runtime: address space conflict: map(0x7f72018000) = 0x7f69ef8000
  fatal error: runtime: address space conflict

  (there is a more detailed write up at https://groups.google.com/d/msg
  /golang-dev/wFW_ppyLZTM/4fJXzuROV1IJ)

  I'm attaching a patch (against gcc-4_8-branch, a different one will be
  required for mainline) that seems to work, but it could certainly do
  with some more extensive testing.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gcc-4.8/+bug/1261604/+subscriptions