rm crashed with SIGSEGV

Bug #359192 reported by Danilo
6
Affects Status Importance Assigned to Milestone
coreutils (Ubuntu)
Invalid
Undecided
Unassigned
glibc (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: coreutils

ubuntu@ubuntu-desktop:~$ lsb_release -rd
Description: Ubuntu jaunty (development branch)
Release: 9.04
ubuntu@ubuntu-desktop:~$ apt-cache policy coreutils
coreutils:
  Installato: 6.10-6ubuntu1
  Candidato: 6.10-6ubuntu1
  Tabella versione:
 *** 6.10-6ubuntu1 0
        500 http://archive.ubuntu.com jaunty/main Packages
        100 /var/lib/dpkg/status

ProblemType: Crash
Architecture: amd64
DistroRelease: Ubuntu 9.04
ExecutablePath: /bin/rm
Package: coreutils 6.10-6ubuntu1
ProcAttrCurrent: unconfined
ProcCmdline: rm -rf /tmp/dpkgrijRs9
ProcEnviron:
 LANGUAGE=it_IT:it:en_GB:en
 LANG=it_IT.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: coreutils
StacktraceTop:
 ?? () from /lib64/ld-linux-x86-64.so.2
 ?? () from /lib64/ld-linux-x86-64.so.2
 ?? () from /lib64/ld-linux-x86-64.so.2
 ?? () from /lib/libc.so.6
 ?? () from /lib/libc.so.6
Title: rm crashed with SIGSEGV
Uname: Linux 2.6.28-11-generic x86_64
UserGroups: adm admin audio cdrom dialout dip fax fuse lpadmin netdev plugdev sambashare scanner tape video

Revision history for this message
Danilo (danilo86) wrote :
visibility: private → public
Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt (retraced)

StacktraceTop:?? ()
?? ()
?? ()
?? ()

Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt (retraced)
tags: added: apport-failed-retrace
tags: removed: need-amd64-retrace
Revision history for this message
C de-Avillez (hggdh2) wrote :

I am having a real problem seeing this as a 'rm' (and, by extension, coreutils) issue: although apport failed on the retrace, the original stacktrace shows only frames from glibc and ld-linux-x86-64.so... so this happened very early in the startup, seemingly *before* control was given to 'rm'.

So... I am adding a task on glibc, and would like the input from the glibc maintainers.

Revision history for this message
C de-Avillez (hggdh2) wrote :

@Danilo: can you tell us what was going on when you got this SEGV?

Changed in coreutils (Ubuntu):
status: New → Incomplete
Revision history for this message
Danilo (danilo86) wrote :

I do not remember now.

Revision history for this message
dino99 (9d9) wrote :

This version has died long ago; no more supported

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