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

Bug #1261604 reported by Michael Hudson-Doyle
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gcc-4.8 (Ubuntu)
Fix Released
Undecided
Unassigned

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.

Tags: patch
Revision history for this message
Michael Hudson-Doyle (mwhudson) wrote :
Revision history for this message
Ubuntu Foundations Team Bug Bot (crichton) wrote :

The attachment "explicit-reservation.diff" seems to be a patch. If it isn't, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issues please contact him.]

tags: added: patch
Revision history for this message
Launchpad Janitor (janitor) wrote :

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 <email address hidden> Fri, 20 Dec 2013 18:24:08 +0100

Changed in gcc-4.8 (Ubuntu):
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.