Bug 592847 - [abrt] crash in clamav-0.95.3-1301.fc13: memcpy: Process /usr/bin/clamscan was killed by signal 7 (SIGBUS)
Summary: [abrt] crash in clamav-0.95.3-1301.fc13: memcpy: Process /usr/bin/clamscan wa...
Status: CLOSED NEXTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: clamav   
(Show other bugs)
Version: 13
Hardware: x86_64
OS: Linux
low
medium
Target Milestone: ---
Assignee: Enrico Scholz
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:1618d1f67f11b5dbb669057411b...
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-05-17 07:21 UTC by Sylvain Réault
Modified: 2011-03-05 01:55 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2011-03-05 01:55:08 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
File: backtrace (31.56 KB, text/plain)
2010-05-17 07:21 UTC, Sylvain Réault
no flags Details

Description Sylvain Réault 2010-05-17 07:21:48 UTC
abrt 1.1.0 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: clamscan -v --exclude=/home/sylvain/.klamav/quarantine -d /home/sylvain/.klamav/database -r --block-encrypted --detect-broken /media/HDD/
component: clamav
crash_function: memcpy
executable: /usr/bin/clamscan
global_uuid: 1618d1f67f11b5dbb669057411bade2be3845537
kernel: 2.6.33.3-85.fc13.x86_64
package: clamav-0.95.3-1301.fc13
rating: 4
reason: Process /usr/bin/clamscan was killed by signal 7 (SIGBUS)
release: Fedora release 13 (Goddard)

How to reproduce
-----
1. For scan NTFS
2. Stop scan
3. forced reload scan

Comment 1 Sylvain Réault 2010-05-17 07:21:50 UTC
Created attachment 414468 [details]
File: backtrace

Comment 2 Nick Bebout 2011-03-05 01:55:08 UTC
0.97 should appear soon.  Please reopen this or open a new bug if you are still experiencing difficulties.


Note You need to log in before you can comment on or make changes to this bug.