Reio,

Sorry about that!  It looks like you've encountered this bug: 
https://bugzilla.clamav.net/show_bug.cgi?id=12412
Will make sure it is fixed soon.

-MIcah

On 10/31/19, 5:21 AM, "clamav-users on behalf of Reio Remma via clamav-users" 
<[email protected] on behalf of 
[email protected]> wrote:

    On 31/10/2019 01:08, Reio Remma via clamav-users wrote:
    > Hello!
    >
    > I started testing 0.102.0 today, but I'm running into problems with 
    > freshclam.
    >
    > Compiled from source on CentOS 8:
    >
    > $ sudo /usr/local/bin/freshclam
    > ClamAV update process started at Thu Oct 31 01:04:40 2019
    > ERROR: Failed to change back to original directory /my/current/dir
    > double free or corruption (top)
    > Aborted 
    
    Well, I solved it!
    
    If I cd to /var/lib/clamav where the databases are, it doesn't need to 
    chdir back to wherever the working dir was when the script was started.
    
    The bit of code that is failing:
    
    libreshclam.c
    
         if (currDir[0] != '\0') {
             /* Restore CWD */
             if (chdir(currDir)) {
                 logg("!Failed to change back to original directory %s\n", 
    currDir);
                 status = FC_EDIRECTORY;
                 goto done;
             }
             logg("*Current working dir restored to %s\n", currDir);
         }
    
    I suspect it's simply a permissions issue.
    
    Good luck,
    Reio
    
    _______________________________________________
    
    clamav-users mailing list
    [email protected]
    https://lists.clamav.net/mailman/listinfo/clamav-users
    
    
    Help us build a comprehensive ClamAV guide:
    https://github.com/vrtadmin/clamav-faq
    
    http://www.clamav.net/contact.html#ml
    


_______________________________________________

clamav-users mailing list
[email protected]
https://lists.clamav.net/mailman/listinfo/clamav-users


Help us build a comprehensive ClamAV guide:
https://github.com/vrtadmin/clamav-faq

http://www.clamav.net/contact.html#ml

Reply via email to