file differently
> >> than other file systems. What is more typical is a read error if you
> seek
> >> outside of the file and then read. Anyhow, if you can identify any
> samples
> >> that cause the issue I'd like to test with it.
> >>>
> >>
Hello Mark,
Thank you, I will look into this. I did some test scans yesterday on 99.2 and
99.3 in mac OS X 10.13 but wasn’t lucky enough to generate the error that you
are seeing. I Will continue to run more scans and see if happens.
Thank you,
Tom M
On 10/31/17, 8:46 AM, "Mark Allan"
Hi folks,
I've attached the output from 3 scans, all of which were started at root (/)
with no other volumes mounted on the system.
I'm running the scans with parameters -riv (recursive, print infected only,
verbose) as well as --debug. The verbose flag prints out the name of each file
being
stems. What is more typical is a read error if you seek
>> outside of the file and then read. Anyhow, if you can identify any samples
>> that cause the issue I'd like to test with it.
>>>
>>> Can you send us your patch to tweak the switch statement for review? I
>&
review? I
> agree that a seek error in one file shouldn't halt the entire scan.
> >
> > Cheers,
> > Micah
> >
> > Micah Snyder
> > Software Engineer
> > Talos Intelligence
> > Cisco Systems, Inc.
> >
> > -Original Message---
t; -Original Message-
> From: clamav-devel [mailto:clamav-devel-boun...@lists.clamav.net] On Behalf
> Of Mark Allan
> Sent: Friday, October 27, 2017 10:44 AM
> To: ClamAV Development <clamav-devel@lists.clamav.net>
> Subject: [Clamav-devel] Why is error 13 fatal?
>
] On Behalf Of
Mark Allan
Sent: Friday, October 27, 2017 10:44 AM
To: ClamAV Development <clamav-devel@lists.clamav.net>
Subject: [Clamav-devel] Why is error 13 fatal?
Hi there,
For a while now, ClamAV 0.99.2 has been terminating unexpectedly with error 13
when running on the latest v
Hi there,
For a while now, ClamAV 0.99.2 has been terminating unexpectedly with error 13
when running on the latest version of OS X (macOS 10.13) but only on drives
formatted with the new APFS, so I chalked it up to an APFS issue and reported
it to Apple. Today, however, I received a report
