freshclam crashed with SIGSEGV

Bug #750181 reported by Velinion
This bug report is a duplicate of:  Bug #766519: freshclam crashed with SIGSEGV. Edit Remove
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
clamav (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: clamav

Just finished reboot after update from Ubuntu 10.10 to 11.4 beta 1
Crash occurred on login.

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: clamav-freshclam 0.97+dfsg-2ubuntu1
ProcVersionSignature: Ubuntu 2.6.38-7.39-generic 2.6.38
Uname: Linux 2.6.38-7-generic x86_64
Architecture: amd64
Date: Mon Apr 4 00:25:06 2011
ExecutablePath: /usr/bin/freshclam
InstallationMedia: Ubuntu 10.04.2 LTS "Lucid Lynx" - Release amd64 (20110211.1)
ProcCmdline: /usr/bin/freshclam -d --quiet
ProcEnviron:
 PATH=(custom, user)
 LANG=en_US.utf8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7fd601290346: movzbl (%rdx,%rax,1),%r13d
 PC (0x7fd601290346) ok
 source "(%rdx,%rax,1)" (0x017d0000) not located in a known VMA region (needed readable region)!
 destination "%r13d" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: clamav
StacktraceTop:
 ?? () from /usr/lib/libclamav.so.6
 ?? () from /usr/lib/libclamav.so.6
 ?? () from /usr/lib/libclamav.so.6
 ?? () from /usr/lib/libclamav.so.6
 ?? () from /usr/lib/libclamav.so.6
Title: freshclam crashed with SIGSEGV
UpgradeStatus: Upgraded to natty on 2011-04-04 (0 days ago)
UserGroups:

Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #743608, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.

visibility: private → public
tags: removed: need-amd64-retrace
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.