<mailto:clamav-devel-boun...@lists.clamav.net>>
> Date: Tuesday, June 2, 2020 at 11:04 AM
> To: ClamAV Development <mailto:clamav-devel@lists.clamav.net>>
> Subject: Re: [Clamav-devel] ClamAV 0.102.3 - Can't allocate memory ERROR on
> macOS 10.15
> Hi M
?
-Micah
From: clamav-devel
Date: Tuesday, June 2, 2020 at 11:04 AM
To: ClamAV Development
Subject: Re: [Clamav-devel] ClamAV 0.102.3 - Can't allocate memory ERROR on
macOS 10.15
Hi Micah,
Thanks. I've uploaded it to clamav.net <http://clamav.net/> as an FP report.
Here are the various
m: clamav-devel
> Date: Friday, May 29, 2020 at 7:46 PM
> To: ClamAV Development
> Subject: Re: [Clamav-devel] ClamAV 0.102.3 - Can't allocate memory ERROR on
> macOS 10.15
> Quick follow-up to this one.
>
> Upon further digging, if the --fdpass flag is passed to clamdsc
allocate memory ERROR on
macOS 10.15
Quick follow-up to this one.
Upon further digging, if the --fdpass flag is passed to clamdscan, you get
different output...albeit still very wrong!
/Applications/Microsoft
Excel.app/Contents/SharedSupport/Microsoft.Mashup.Container.app/Contents
Quick follow-up to this one.
Upon further digging, if the --fdpass flag is passed to clamdscan, you get
different output...albeit still very wrong!
/Applications/Microsoft
Excel.app/Contents/SharedSupport/Microsoft.Mashup.Container.app/Contents/SharedSupport/System.ValueTuple.dll:
Hi there,
On Fri, 29 May 2020, Mark Allan wrote:
... testing 0.102.3 ... Can't allocate memory ERROR ...
...
Removing the ... definition ... feels like ... the wrong solution ...
Agreed. :)
Has anyone else come up against this problem before, and do you know
what I can do about it?
No, I
Hi folks,
I'm still testing 0.102.3 but I've hit a few issues where some known-good files
are being detected as infected because they're generating the following error:
Can't allocate memory ERROR
Output from clamscan and clamdscan are as follows:
> $ /usr/local/bin/clamscan
