Sergey wrote:
> Is this the gcc 4.1.0 bug only ? What about 3.4.4 and 3.3.3 ?
Hi Sergey,
no other reports so far, besides 4.1.0 which is b0rked and will likely
be blacklisted starting from the next release.
It's unfortunate that some distro has got it installed by default.
-aCaB
_
On Tuesday 04 September 2007, aCaB wrote:
> Looks to me like a compiler bug.
> If you're using gcc 4.1.0 do yourself a favour and upgrade to at least
> 4.1.1.
>
> Please see https://wwws.clamav.net/bugzilla/show_bug.cgi?id=613
Is this the gcc 4.1.0 bug only ? What about 3.4.4 and 3.3.3 ?
--
Re
To: ClamAV Development
Subject: Re: [Clamav-devel] Segfault in libclamav (0.91.2)
Gregory Nietsky wrote:
>
> Greetings all ...
>
> Here is a regression fix to a bug causing a segfault on some files ...
>
> The trick might be to check for dcur+unp_offset+i<0 aswell as u
Subject: Re: [Clamav-devel] Segfault in libclamav (0.91.2)
Gregory Nietsky wrote:
>
> Greetings all ...
>
> Here is a regression fix to a bug causing a segfault on some files ...
>
> The trick might be to check for dcur+unp_offset+i<0 aswell as unp_offset
Hi Gregory,
Looks
Gregory Nietsky wrote:
>
> Greetings all ...
>
> Here is a regression fix to a bug causing a segfault on some files ...
>
> The trick might be to check for dcur+unp_offset+i<0 aswell as unp_offset
Hi Gregory,
Looks to me like a compiler bug.
If you're using gcc 4.1.0 do yourself a favour and
