Red Hat Bugzilla – Bug 1016666
[abrt] clamav-0.98-1.fc20: memset: Process /usr/bin/clamscan was killed by signal 11 (SIGSEGV)
Last modified: 2015-06-29 08:35:18 EDT
Description of problem:
Logged into Cinnamon Desktop and found this error waiting for me. I was doing nothing previous to this and was running no applications. So, I do not know the cause or how it may be reproduced.
Version-Release number of selected component:
cmdline: /usr/bin/clamscan --exclude-dir=.thunderbird --exclude-dir=.mozilla-thunderbird --exclude-dir=.evolution --exclude-dir=Mail --exclude-dir=kmail --detect-pua -i -r /home/dcpyle --exclude-dir=/home/dcpyle/.clamtk/viruses --exclude-dir=/usr/lib/vmware/isoimages --exclude-dir=/usr/lib/python2.7/site-packages/virtualenv_support --log=/home/dcpyle/.clamtk/history/Oct-08-2013.log
runlevel: N 5
Thread no. 1 (10 frames)
#0 memset at ../sysdeps/x86_64/memset.S:97
#2 cl_fmap_open_handle at fmap.c:247
#3 fmap_check_empty at fmap.c:87
#4 fmap at fmap.c:717
#5 cli_magic_scandesc at scanners.c:2801
#6 scan_common at scanners.c:2933
#7 cl_scandesc_callback at scanners.c:2952
#8 scanfile at manager.c:295
#9 scandirs at manager.c:427
#12 scanmanager at manager.c:939
Created attachment 809291 [details]
Created attachment 809292 [details]
Created attachment 809293 [details]
Created attachment 809294 [details]
Created attachment 809295 [details]
Created attachment 809296 [details]
Created attachment 809297 [details]
Created attachment 809298 [details]
Created attachment 809299 [details]
Created attachment 809300 [details]
Created attachment 809301 [details]
Crash just happened again. This time I was surfing the web using Firefox.
I am seeing these crashes fairly regularly. I think I know the cause, now. It looks like the crash occurs whenevere clamscan tries to scan a VMware Player Virtual Machine hard drive file. Each and every time it segfaults as soon as I see the file's name listed in the output. It is 100% reproducible. I ended up having to remove my crontab so I wouldn't see this error every hour or so. Here is the short version of the output when scanning the culprit directory:
$ clamscan --debug -rvi ~/.vmware 2>/dev/null
Scanning /home/dcpyle/.vmware/Windows XP Mode/vmware-1.log
Scanning /home/dcpyle/.vmware/Windows XP Mode/vmmcores-2.gz
Scanning /home/dcpyle/.vmware/Windows XP Mode/Windows XP Mode.vmdk
Segmentation fault (core dumped)
cmdline: clamscan --debug -rvi /home/dcpyle/.vmware
reason: Process /usr/bin/clamscan was killed by signal 11 (SIGSEGV)
reported_to: uReport: BTHASH=a501f228e3437d8a03ea0f73e07ed1bf037e60a9
runlevel: N 5
This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora 'version'
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.
Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 20 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
Thank you for reporting this bug and we are sorry it could not be fixed.