cp crashed with SIGSEGV in __libc_start_main()

Bug #865288 reported by Xilmwa
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
coreutils (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Booted to a desktop and got this.

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: coreutils 8.5-1ubuntu6
ProcVersionSignature: Ubuntu 3.0.0-12.19-generic 3.0.4
Uname: Linux 3.0.0-12-generic i686
NonfreeKernelModules: nvidia
ApportVersion: 1.23-0ubuntu2
Architecture: i386
Date: Mon Oct 3 00:58:52 2011
Disassembly: => 0x6049728: Cannot access memory at address 0x6049728
ExecutablePath: /bin/cp
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1)
ProcCmdline: cp -f /var/run/pm-utils/pm-suspend/storage/parameters.new /var/run/pm-utils/pm-suspend/storage/parameters
ProcEnviron:
 PATH=(custom, no user)
 LC_COLLATE=C
SegvAnalysis:
 Segfault happened at: 0x6049728: Cannot access memory at address 0x6049728
 PC (0x06049728) not located in a known VMA region (needed executable region)!
SegvReason: executing unknown VMA
Signal: 11
SourcePackage: coreutils
StacktraceTop:
 ?? ()
 ?? ()
 __libc_start_main () from /lib/i386-linux-gnu/libc.so.6
 ?? ()
Title: cp crashed with SIGSEGV in __libc_start_main()
UpgradeStatus: Upgraded to oneiric on 2011-10-02 (1 days ago)
UserGroups:

Revision history for this message
Xilmwa (xilmwa) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 ?? ()
 __libc_csu_init ()
 __libc_start_main (main=0x804b400 <main>, argc=4, ubp_av=0xbfd63164, init=0x805c960 <__libc_csu_init>, fini=0x805c9c0 <__libc_csu_fini>, rtld_fini=0x77abc0, stack_end=0xbfd6315c) at libc-start.c:185
 _start ()

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in coreutils (Ubuntu):
importance: Undecided → Medium
tags: removed: need-i386-retrace
C de-Avillez (hggdh2)
visibility: private → public
Revision history for this message
dino99 (9d9) wrote :

This version has expired long time ago, and is no more supported

Changed in coreutils (Ubuntu):
status: New → 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.