lsb_release crashed with SIGSEGV in _IO_un_link()

Bug #435617 reported by Goldy
26
This bug affects 5 people
Affects Status Importance Assigned to Milestone
lsb (Ubuntu)
New
Medium
Unassigned

Bug Description

Binary package hint: lsb

amd64 dual core, 4gb RAM

ProblemType: Crash
Architecture: amd64
Date: Thu Sep 24 06:09:10 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/lsb_release
InterpreterPath: /usr/bin/python2.6
Package: lsb-release 4.0-0ubuntu4
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/lsb_release -c -s
ProcEnviron:
 LANGUAGE=he_IL.UTF-8
 LANG=he_IL.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-10.35-generic
Signal: 11
SourcePackage: lsb
StacktraceTop:
 _IO_un_link () from /lib/libc.so.6
 fclose () from /lib/libc.so.6
 ?? ()
 ?? ()
 ?? ()
Title: lsb_release crashed with SIGSEGV in _IO_un_link()
Uname: Linux 2.6.31-10-generic x86_64
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
SegvAnalysis:
 Segfault happened at: 0x7fff494f7268 <_IO_un_link+504>: callq *%rax
 PC (0x7fff494f7268) ok
 source "*%rax" (0xc1d9f6614237c286) not located in a known VMA region (needed readable region)!
 destination "(%rsp)" (0x7fff497f4f10) ok
SegvReason: reading unknown VMA

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

StacktraceTop:_IO_un_link (fp=0x24bd590) at genops.c:69
_IO_new_fclose (fp=0x24bd590) at iofclose.c:58
load_source_module (name=0x7fff497f7180 "abc",
import_submodule (mod=0x81b5c0,
load_next (mod=0x81b5c0,

Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt (retraced)
Changed in lsb (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Kees Cook (kees)
description: updated
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.