8l crashed with SIGSEGV

Bug #976418 reported by Сергей Иванников
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
golang (Ubuntu)
Invalid
Medium
Сергей Иванников

Bug Description

ubuntu 12.04, processor Intel atom d410

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: golang-go 2:1-2
ProcVersionSignature: Ubuntu 3.2.0-22.35-generic-pae 3.2.14
Uname: Linux 3.2.0-22-generic-pae i686
ApportVersion: 2.0-0ubuntu4
Architecture: i386
Date: Sun Apr 8 13:56:19 2012
ExecutablePath: /usr/lib/go/pkg/tool/linux_386/8l
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha i386 (20111129.1)
ProcCmdline: /usr/lib/go/pkg/tool/linux_386/8l -o habr -L /tmp/go-build428488674 /tmp/go-build428488674/command-line-arguments.a
ProcEnviron:
 SHELL=/bin/bash
 TERM=xterm
 PATH=(custom, user)
 LANG=ru_RU.UTF-8
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: golang
Stacktrace:
 #0 0x0804fb9b in ?? ()
 No symbol table info available.
 Cannot access memory at address 0xbf9bbccc
StacktraceTop: ?? ()
Title: 8l crashed with SIGSEGV
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
Сергей Иванников (ivannixs) wrote :
Changed in golang (Ubuntu):
assignee: nobody → Сергей Иванников (ivannixs)
Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : StacktraceTop.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in golang (Ubuntu):
importance: Undecided → Medium
tags: removed: need-i386-retrace
Revision history for this message
Matthias Klose (doko) wrote :

please tell how to reproduce this.

information type: Private → Public
Changed in golang (Ubuntu):
status: New → Incomplete
Revision history for this message
Michael Hudson-Doyle (mwhudson) wrote :

Assuming this is no longer relevant.

Changed in golang (Ubuntu):
status: Incomplete → Invalid
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.