nscd crashed with SIGSEGV in gc()

Bug #271423 reported by Adam Petaccia
6
Affects Status Importance Assigned to Milestone
glibc (Ubuntu)
New
Undecided
Unassigned

Bug Description

I wasn't doing anything at the time, although I will provide any needed info.

ProblemType: Crash
Architecture: amd64
CrashCounter: 1
Dependencies:
 libgcc1 1:4.3.2-1ubuntu7 [modified: lib/libgcc_s.so.1]
 gcc-4.3-base 4.3.2-1ubuntu7
 findutils 4.4.0-2ubuntu3 [modified: usr/bin/xargs usr/bin/find usr/bin/oldfind]
 libc6 2.8~20080505-0ubuntu6 [modified: lib/ld-2.8.90.so lib/libc-2.8.90.so lib/libcrypt-2.8.90.so lib/libdl-2.8.90.so lib/libm-2.8.90.so lib/libnsl-2.8.90.so lib/libpthread-2.8.90.so lib/libresolv-2.8.90.so lib/librt-2.8.90.so lib/libthread_db-1.0.so lib/libutil-2.8.90.so usr/lib/pt_chown usr/bin/iconv usr/bin/getent usr/bin/getconf usr/bin/zdump usr/bin/rpcinfo usr/sbin/zic usr/sbin/iconvconfig]
DistroRelease: Ubuntu 8.10
ExecutablePath: /usr/sbin/nscd
NonfreeKernelModules: nvidia
Package: nscd 2.8~20080505-0ubuntu6
ProcAttrCurrent: unconfined
ProcCmdline: /usr/sbin/nscd
ProcEnviron: PATH=/sbin:/usr/sbin:/bin:/usr/bin
Signal: 11
SourcePackage: glibc
StacktraceTop:
 gc () from /usr/sbin/nscd
 prune_cache () from /usr/sbin/nscd
 nscd_run_prune () from /usr/sbin/nscd
 start_thread () from /lib/libpthread.so.0
 clone () from /lib/libc.so.6
Title: nscd crashed with SIGSEGV in gc()
Uname: Linux 2.6.27-rc5regressiontest x86_64
UserGroups:

Revision history for this message
Adam Petaccia (mighmos) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:?? () from /usr/sbin/nscd
?? () from /usr/sbin/nscd
?? () from /usr/sbin/nscd
start_thread () from /lib/libpthread.so.0
clone () from /lib/libc.so.6

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
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.