I use clamd with Amavisd on a PowerPC G4 (32 bits) running Gentoo Linux. ClamAV version considered stable by the Gentoo team is 0.99, but I reproduced the bug with 0.98.7 and 0.99.2 (compiled from Gentoo packages). Until Thursday 16 June, it was working properly. But starting on « Thursday 16 Jun 2016 08:07:40 -0000 », Amavis indicates that e-mails are unchecked, and when I try to launch clamd on a command line, I get the error: # /usr/sbin/clamd --debug clamd: llvm/lib/Target/PowerPC/PPCJITInfo.cpp:399: virtual void llvm::PPCJITInfo::relocate(void*, llvm::MachineRelocation*, unsigned int, unsigned char*): Assertion `ResultPtr >= -(1 << 23) && ResultPtr < (1 << 23) && "Relocation out of range!"' failed. Aborted and clamav doesn't launch. llvm is in version 3.5.0. No software update has been performed this day, but there may have been database updates through Freshclam. Reproducible: Always Steps to Reproduce: 1. Execute: # /usr/sbin/clamd --debug Actual Results: clamd: llvm/lib/Target/PowerPC/PPCJITInfo.cpp:399: virtual void llvm::PPCJITInfo::relocate(void*, llvm::MachineRelocation*, unsigned int, unsigned char*): Assertion `ResultPtr >= -(1 << 23) && ResultPtr < (1 << 23) && "Relocation out of range!"' failed. Aborted Expected Results: Alternatively, try to launch the deamon using /etc/init.d scripts: # /etc/init.d/clamd restart * Stopping clamd ... * start-stop-daemon: no matching processes found [ ok ] * Stopping freshclam ... [ ok ] * Starting clamd ... * start-stop-daemon: failed to start `/usr/sbin/clamd' * Failed to start clamd [ !! ] * Starting freshclam ... [ ok ] I already reported the bug upstream one month ago but got no answer. https://bugzilla.clamav.net/show_bug.cgi?id=11590 There may be here some other guys using ClamAv on PPC32 and being able to confirm or not the bug.
Created attachment 440956 [details] emerge --info output
on ppc64 it doesn't start either: clamd: llvm/lib/Target/PowerPC/PPCCodeEmitter.cpp:156: unsigned int {anonymous}::PPCCodeEmitter::getMachineOpValue(const llvm::MachineInstr&, const llvm::MachineOperand&): Assertion `MovePCtoLROffset && "MovePCtoLR not seen yet?"' failed. Abort
0.99.4 appears to work for me.
Thanks @grobian since this is llvm related and llvm is pretty much depreciated (especially from 0.100.0 ) I am closing this bug now. should there still be an issue, please re-open it
