apt-check crashed with signal 7 in strlen()

Bug #301220 reported by Laurent Bonnaud
14
Affects Status Importance Assigned to Milestone
update-notifier (Ubuntu)
Incomplete
Undecided
Unassigned

Bug Description

Binary package hint: update-notifier

When this crash happened, I was running the following command in a root shell:

dselect update; apt-get -u dist-upgrade ; apt-get clean

ProblemType: Crash
Architecture: i386
DistroRelease: Ubuntu 8.10
ExecutablePath: /usr/lib/update-notifier/apt-check
InterpreterPath: /usr/bin/python2.5
NonfreeKernelModules: fglrx
Package: update-notifier 0.71.8 [modified: usr/bin/update-notifier]
ProcAttrCurrent: unconfined
ProcCmdline: /usr/bin/python /usr/lib/update-notifier/apt-check
ProcEnviron:
 LC_PAPER=fr_FR.UTF-8
 SHELL=/bin/bash
 PATH=/home/User Name/local/linux/bin:.:/home/User Name/local/share/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/bin/X11:/usr/games
 LC_COLLATE=C
 LANG=en_US.UTF-8
Signal: 7
SourcePackage: update-notifier
StacktraceTop:
 strlen () from /lib/tls/i686/cmov/libc.so.6
 std::string::compare () from /usr/lib/libstdc++.so.6
 debPackagesIndex::FindInCache ()
 ?? () from /usr/lib/libapt-pkg-libc6.8-6.so.4.6
 pkgMakeStatusCache ()
Title: apt-check crashed with signal 7 in strlen()
Uname: Linux 2.6.27-8-generic i686
UserGroups: adm admin audio cdrom dialout dip floppy fuse kvm lpadmin plugdev pulse-rt scanner staff video

Revision history for this message
Laurent Bonnaud (laurent-bonnaud) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:strlen () from /lib/tls/i686/cmov/libc.so.6
?? ()
?? ()
?? ()
?? ()

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
Revision history for this message
Jonathan Thomas (echidnaman) wrote :

Is this crash reproducible? Unfortunately apport was not able to get a good backtrace.

Changed in update-notifier:
status: New → Incomplete
Revision history for this message
Laurent Bonnaud (laurent-bonnaud) wrote :

Unfortunately, no.

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.