Bug 12661 - LibClamAV warning while clamscan -i --recursive=yes --remove=yes -z -l ~/mylog /home
LibClamAV warning while clamscan -i --recursive=yes --remove=yes -z -l ~/myl...
Status: CLOSED NEEDINFO
Product: ClamAV
Classification: ClamAV
Component: clamscan
stable
x86_64 GNU/Linux
: P3 normal
: 0.101.0
Assigned To: ClamAV team
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2021-01-13 00:08 EST by Richard Shards
Modified: 2021-04-01 16:52 EDT (History)
2 users (show)

See Also:
QA Contact:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Richard Shards 2021-01-13 00:08:39 EST
After doing this 

 clamscan -i --recursive=yes --remove=yes  -z -l ~/mylog /home

I get this

LibClamAV Error: cli_calloc(): Attempt to allocate 0 bytes. Please report to https://bugzilla.clamav.net
LibClamAV Warning: fmap: map header allocation failed
LibClamAV Error: CRITICAL: fmap() failed
LibClamAV Error: CRITICAL: fmap() failed
LibClamAV Error: CRITICAL: fmap() failed
Comment 1 Micah Snyder 2021-01-13 14:48:05 EST
Hi Richard,

Thanks for reporting the issue. The error message you're seeing would be from scanning a specific file.  When using clamscan, the name of the file should come directly after the error messages.  If you're able to share this file, we would need a copy to be able to reproduce the error and identify what caused the error.

You can add the attachment directly to this ticket.  If necessary, you can mark it as private so that the public cannot view it.

-Micah
Comment 2 Micah Snyder 2021-04-01 16:52:23 EDT
Without test files or additional information I won't be able to help solve this.  I'm going to close the ticket, but feel free to reopen it if you find a files that I can test with to reproduce the issue.