Also, I confirm the existence of a working socket appropriate for the --fdpass flag:
> ls -l /opt/local/var/run/clamav/clamd.socket > srw-rw-rw- 1 root _clamav 0 Apr 10 14:53 > /opt/local/var/run/clamav/clamd.socket= > On Apr 11, 2021, at 3:44 PM, Steven Smith <steve.t.sm...@gmail.com> wrote: > > Passing the flag --fdpass causes a segmentation fault with clamdscan (v. > 0.103.2/26102) on macOS (10.15). > > This issue arose about 6 months ago, > > Here's What I see from a core dump: > > Dump core: > >> sudo clamdscan --multiscan --quiet --fdpass --move=/opt/Quarantine/ >> --log=/opt/local/var/log/clamav/ClamavScanSchedule.log >> Segmentation fault: 11 > > Stack trace: > >> $ lldb `which clamdscan` -c /cores/core.67147 >> (lldb) target create "/opt/local/bin/clamdscan" --core "/cores/core.67147" >> Core file '/cores/core.67147' (x86_64) was loaded. >> >> (lldb) bt all >> * thread #1, stop reason = signal SIGSTOP >> * frame #0: 0x00007fff67ef8bb0 libsystem_platform.dylib`_platform_strncpy + >> 112 >> frame #1: 0x000000010801c086 clamdscan`match_regex + 129 >> frame #2: 0x0000000108018af0 clamdscan`chkpath + 64 >> frame #3: 0x0000000108019205 clamdscan`parallel_callback + 110 >> frame #4: 0x00000001081841c1 libclamav.9.dylib`cli_ftw + 271 >> frame #5: 0x00000001080190d6 clamdscan`parallel_client_scan + 172 >> frame #6: 0x000000010801a2d4 clamdscan`client_scan + 222 >> frame #7: 0x000000010801a1b0 clamdscan`client + 940 >> frame #8: 0x0000000108017f3c clamdscan`main + 728 >> frame #9: 0x00007fff67d01cc9 libdyld.dylib`start + 1 > > > Reference: > https://trac.macports.org/ticket/62369#comment:5
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ clamav-devel mailing list clamav-devel@lists.clamav.net https://lists.clamav.net/mailman/listinfo/clamav-devel Please submit your patches to our Github: https://github.com/Cisco-Talos/clamav-devel/pulls Help us build a comprehensive ClamAV guide: https://github.com/vrtadmin/clamav-faq http://www.clamav.net/contact.html#ml
