Ubuntu
coreutils package

ls crashed with SIGILL in setlocale()

Bug #346045 reported by aguy on 2009-03-20

6

Affects		Status	Importance	Assigned to	Milestone
	coreutils (Ubuntu)	Invalid	Medium	Unassigned
	glibc (Ubuntu)	Invalid	Undecided	Unassigned

Bug Description

Binary package hint: coreutils

no idea why it crashed ?

ProblemType: Crash
Architecture: i386
DistroRelease: Ubuntu 9.04
ExecutablePath: /bin/ls
NonfreeKernelModules: nvidia
Package: coreutils 6.10-6ubuntu1
ProcAttrCurrent: unconfined
ProcCmdline: ls -1 *.ppd
ProcEnviron:
SHELL=/bin/bash
PATH=(custom, no user)
LANG=en_GB.UTF-8
Signal: 4
SourcePackage: coreutils
Stacktrace:
#0 0xb7dc6f14 in ?? () from /lib/tls/i686/cmov/libc.so.6
#1 0xb7dc6822 in setlocale () from /lib/tls/i686/cmov/libc.so.6
#2 0x0804f763 in ?? ()
#3 0xb7dbb775 in __libc_start_main () from /lib/tls/i686/cmov/libc.so.6
#4 0x08049b41 in ?? ()
StacktraceTop:
?? () from /lib/tls/i686/cmov/libc.so.6
setlocale () from /lib/tls/i686/cmov/libc.so.6
?? ()
__libc_start_main () from /lib/tls/i686/cmov/libc.so.6
?? ()
Title: ls crashed with SIGILL in setlocale()
Uname: Linux 2.6.28-8-generic i686
UserGroups:

Tags:

Revision history for this message

aguy (astyguy-deactivatedaccount) wrote on 2009-03-20:

#1

Dependencies.txt Edit (160 bytes, text/plain; charset="utf-8")
Disassembly.txt Edit (491 bytes, text/plain; charset="utf-8")
ProcMaps.txt Edit (2.3 KiB, text/plain; charset="utf-8")
ProcStatus.txt Edit (714 bytes, text/plain; charset="utf-8")
Registers.txt Edit (470 bytes, text/plain; charset="utf-8")
ThreadStacktrace.txt Edit (271 bytes, text/plain; charset="utf-8")

Revision history for this message

Apport retracing service (apport) wrote on 2009-03-26: Symbolic stack trace

#2

Stacktrace.txt (retraced) Edit (1.2 KiB, text/plain)

StacktraceTop:_nl_find_locale (locale_path=0x0, locale_path_len=0,
*__GI_setlocale (category=12, locale=0x805cd8e "")
main (argc=3, argv=0xbff72844) at ls.c:1144

Revision history for this message

Apport retracing service (apport) wrote on 2009-03-26: Symbolic threaded stack trace

#3

ThreadStacktrace.txt (retraced) Edit (1.3 KiB, text/plain)

Changed in coreutils:
importance:	Undecided → Medium

Revision history for this message

C de-Avillez (hggdh2) wrote on 2009-04-13:

#4

The stacktrace shows clearly the top-of-stack being a function in LIBC6. As such, closing INVALID coreutils, and opening a new task on glibc.

Changed in coreutils (Ubuntu):
status:	New → Invalid

Revision history for this message

Matthias Klose (doko) wrote on 2009-04-13:

#5

> The stacktrace shows clearly the top-of-stack being a function in LIBC6. As such,
> closing INVALID coreutils, and opening a new task on glibc.

Don't do this, unless you are certain that the cause for this is in glibc. Just showing "the top-of-stack being a function in LIBC6" is not a reason at all.

Changed in coreutils (Ubuntu):
status:	Invalid → New
Changed in glibc (Ubuntu):
status:	New → Incomplete

Revision history for this message

dino99 (9d9) wrote on 2016-01-23:

#6

This version has died long ago; no more supported

Changed in glibc (Ubuntu):
status:	Incomplete → Invalid
Changed in coreutils (Ubuntu):
status:	New → Invalid

Report a bug

This report contains Public information

Everyone can see this information.

You are

Subscribing...

Edit bug mail

Other bug subscribers

Bug attachments

Add attachment

Remote bug watches

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