su crashed with SIGSEGV in _nss_compat_getpwuid_r()

Bug #606763 reported by Oded Arbel
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
shadow (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Not sure when this happened

ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: login 1:4.1.4.2-1ubuntu2
ProcVersionSignature: Ubuntu 2.6.35-7.12-generic 2.6.35-rc4
Uname: Linux 2.6.35-7-generic x86_64
Architecture: amd64
Date: Sat Jul 17 09:33:14 2010
ExecutablePath: /bin/su
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Alpha amd64 (20100701)
ProcCmdline: su oded.a -c -- pacmd\ list-sinks
ProcEnviron:
 LC_COLLATE=C
 PATH=(custom, no user)
SegvAnalysis:
 Segfault happened at: 0x7fcfea8d8d4c: movb $0xff,(%r12)
 PC (0x7fcfea8d8d4c) ok
 source "$0xff" ok
 destination "(%r12)" (0x7fff464beb6f) not located in a known VMA region (needed writable region)!
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: shadow
StacktraceTop:
 ?? () from /lib/libnss_compat.so.2
 _nss_compat_getpwuid_r ()
 getpwuid_r () from /lib/libc.so.6
 ?? () from /lib/libc.so.6
 getlogin () from /lib/libc.so.6
Title: su crashed with SIGSEGV in _nss_compat_getpwuid_r()
UserGroups:

Revision history for this message
Oded Arbel (oded-geek) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 internal_getpwuid_r (uid=<value optimized out>,
 _nss_compat_getpwuid_r (uid=4294967295,
 __getpwuid_r (uid=4294967295,
 __getlogin_r_loginuid (name=<value optimized out>,
 getlogin ()

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 shadow (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Oded Arbel (oded-geek)
visibility: private → public
Revision history for this message
dino99 (9d9) wrote :

This version is outdated and no more supported

Changed in shadow (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.