<html><body><div style="color:#000; background-color:#fff; font-family:HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif;font-size:12pt"><div style="" class=""><br style=""><span style="" class="" id="yiv8259584773yui_3_16_0_6_1401652886280_16">Thanks for the update, Andreas. It's10960 in the bug tracker, so it must be a commit typo.</span></div> <div class="qtdSeparateBR"><br><br></div><div style="display: block;" class="yahoo_quoted"> <div class="" style="font-family: HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif; font-size: 12pt;"> <div class="" style="font-family: HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif; font-size: 12pt;"> <div style="" class="" dir="ltr"> <font style="" class="" face="Arial" size="2"> On Thursday, May 29, 2014 12:37 PM, Andreas Cadhalpun <andreas.cadhalpun@googlemail.com> wrote:<br style="" class=""> </font> </div> <br style=""
class=""><br style="" class=""> <div style="" class="">Control: tags -1 fixed 0.98.3+dfsg-1<br style="" class="" clear="none"><br style="" class="" clear="none">Hi Pascal,<br style="" class="" clear="none"><div style="" class="" id="yqtfd89665"><br style="" class="" clear="none">On 29.05.2014 12:49, Pascal Meunier wrote:<br style="" class="" clear="none">> I'm filing this bug as requested by Scott Kitterman. The issue has<br style="" class="" clear="none">> been fixed upstream (Bug #10960) by commits<br style="" class="" clear="none">> c6f5ef98d6ab7d3abcd207c25d06eaeb95d68ffc and<br style="" class="" clear="none">> 99ee2138c496d3d51af67e521e945803565b9f7d. Symptoms are segfaults when<br style="" class="" clear="none">> running clamscan, or a report of an invalid pointer by glibc,<br style="" class="" clear="none">> depending on whether a
directory is recursively scanned or a single<br style="" class="" clear="none">> file. I first noticed the reproducible segfault when recursively<br style="" class="" clear="none">> scanning, which started happening immediately after a clamav update.<br style="" class="" clear="none">> When attempting to isolate a single file that would<br style="" class="" clear="none">> cause the issue, I got the invalid pointer report by glibc.</div><br style="" class="" clear="none"><br style="" class="" clear="none">This fix made it into the 0.98.3 release and is already in unstable.<br style="" class="" clear="none">Unfortunately that version fails to build on PowerPC, so it doesn't <br style="" class="" clear="none">migrate to testing and can't be uploaded to wheezy.<br style="" class="" clear="none"><br style="" class="" clear="none">(By the way, the commit message says this fixes upstream
bug #10970, not <br style="" class="" clear="none">#10960, so either there is a typo in the commit message or you meant <br style="" class="" clear="none">#10970.)<br style="" class="" clear="none"><br style="" class="" clear="none">As I don't know, when the PowerPC failure will be fixed, it's probably <br style="" class="" clear="none">best to cherry-pick this fix for wheezy.<br style="" class="" clear="none"><br style="" class="" clear="none">Scott, what do you think?<br style="" class="" clear="none"><br style="" class="" clear="none">Best regards,<br style="" class="" clear="none">Andreas<div style="" class="" id="yqtfd21117"><br style="" class="" clear="none"></div><br style="" class=""><br style="" class=""></div> </div> </div> </div> </div></body></html>