id crashed with SIGSEGV in __libc_start_main()

Bug #127415 reported by Elmer van Baal
This bug report is a duplicate of:  Bug #118840: [apport] id crashed with SIGSEGV. Edit Remove
8
Affects Status Importance Assigned to Milestone
coreutils (Ubuntu)
Incomplete
Medium
Unassigned

Bug Description

don't have a clue

ProblemType: Crash
Architecture: i386
Date: Sat Jul 21 21:00:30 2007
DistroRelease: Ubuntu 7.10
ExecutablePath: /usr/bin/id
NonfreeKernelModules: cdrom
Package: coreutils 5.97-5.3ubuntu1
PackageArchitecture: i386
ProcCmdline: id -u
ProcCwd: /
ProcEnviron:
 SHELL=/bin/bash
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/X11R6/bin
 LANG=en_US.UTF-8
Signal: 11
SourcePackage: coreutils
Stacktrace:
 #0 0x0804aec9 in ?? ()
 #1 0xb7e33fd1 in __libc_start_main () from /lib/tls/i686/cmov/libc.so.6
 #2 0x08048e81 in ?? ()
StacktraceTop:
 ?? ()
 __libc_start_main () from /lib/tls/i686/cmov/libc.so.6
 ?? ()
ThreadStacktrace:
 .
 Thread 1 (process 9237):
 #0 0x0804aec9 in ?? ()
 #1 0xb7e33fd1 in __libc_start_main () from /lib/tls/i686/cmov/libc.so.6
 #2 0x08048e81 in ?? ()
Title: id crashed with SIGSEGV in __libc_start_main()
Uname: Linux elmer-laptop 2.6.22-8-generic #1 SMP Thu Jul 12 15:59:45 GMT 2007 i686 GNU/Linux
UserGroups:

Tags: apport-crash
Revision history for this message
Elmer van Baal (evbaal) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:__libc_csu_init ()
_start ()

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
Changed in coreutils:
importance: Undecided → Medium
Revision history for this message
Hew (hew) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue for you. Can you try with the latest Ubuntu release? Thanks in advance.

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