as crashed with SIGSEGV

Bug #349493 reported by aguy
6
Affects Status Importance Assigned to Milestone
binutils (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Binary package hint: binutils

no idea it just crashed

ProblemType: Crash
Architecture: i386
Dependencies:
 libgcc1 1:4.3.3-5ubuntu4
 zlib1g 1:1.2.3.3.dfsg-12ubuntu2
 gcc-4.3-base 4.3.3-5ubuntu4
 findutils 4.4.0-2ubuntu3
 libc6 2.9-4ubuntu3
DistroRelease: Ubuntu 9.04
ExecutablePath: /usr/bin/as
NonfreeKernelModules: nvidia
Package: binutils 2.19.1-0ubuntu3
ProcAttrCurrent: unconfined
ProcCmdline: as -Qy -o /home/mrasty/.ccache/tmp.hash.hostname.1133.o /tmp/ccyQFmkt.s
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, no user)
 LANG=
Signal: 11
SourcePackage: binutils
Stacktrace:
 #0 0x40000afe in ?? () from /lib/ld-linux.so.2
 #1 0x40000817 in ?? () from /lib/ld-linux.so.2
StacktraceTop:
 ?? () from /lib/ld-linux.so.2
 ?? () from /lib/ld-linux.so.2
ThreadStacktrace:
 .
 Thread 1 (process 1153):
 #0 0x40000afe in ?? () from /lib/ld-linux.so.2
 #1 0x40000817 in ?? () from /lib/ld-linux.so.2
Title: as crashed with SIGSEGV
Uname: Linux 2.6.28-11-generic i686
UserGroups:

Revision history for this message
aguy (astyguy-deactivatedaccount) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:_dl_start (arg=0xbfaa7860) at dynamic-link.h:167
_start () from /lib/ld-linux.so.2

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
Revision history for this message
Apport retracing service (apport) wrote : Stack trace with source code
Changed in binutils:
importance: Undecided → Medium
Revision history for this message
Matthias Klose (doko) wrote :

> no idea it just crashed

that's not much information.

Changed in binutils (Ubuntu):
status: New → Incomplete
Revision history for this message
Matthias Klose (doko) wrote :

closing. please feel free to reopen providing more information.

Changed in binutils (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.