Renato Botelho | 1 Mar 2010 20:22
Picon
Gravatar

Tests failing on FreeBSD 6.x

Hello one more time,

I was trying to update clamav-devel port to a more recent snapshot
and I got some segfaults during make test, like you can see here:

g++42: -rpath=/usr/local/lib/gcc42: linker input file unused because
linking not done
  CXX    llvmunittest_JIT-JITMemoryManagerTest.o
g++42 -DHAVE_CONFIG_H -I.  -I./llvm/include -I./llvm/include
-D__STDC_LIMIT_MACROS -D__STDC_CONSTANT_MACROS -D_DEBUG -D_GNU_SOURCE
-I./llvm/utils/unittest/googletest/include -I/usr/local/include
-Woverloaded-virtual -pedantic -Wno-long-long -Wall -W
-Wno-unused-parameter -Wwrite-strings -Wno-missing-field-initializers
-Wno-variadic-macros -fno-exceptions -O2 -fno-strict-aliasing -pipe
-Wl,-rpath=/usr/local/lib/gcc42 -c -o
llvmunittest_JIT-JITMemoryManagerTest.o `test -f
'llvm/unittests/ExecutionEngine/JIT/JITMemoryManagerTest.cpp' || echo
'./'`llvm/unittests/ExecutionEngine/JIT/JITMemoryManagerTest.cpp
g++42: -rpath=/usr/local/lib/gcc42: linker input file unused because
linking not done
  CXX    llvmunittest_JIT-JITTest.o
g++42 -DHAVE_CONFIG_H -I.  -I./llvm/include -I./llvm/include
-D__STDC_LIMIT_MACROS -D__STDC_CONSTANT_MACROS -D_DEBUG -D_GNU_SOURCE
-I./llvm/utils/unittest/googletest/include -I/usr/local/include
-Woverloaded-virtual -pedantic -Wno-long-long -Wall -W
-Wno-unused-parameter -Wwrite-strings -Wno-missing-field-initializers
-Wno-variadic-macros -fno-exceptions -O2 -fno-strict-aliasing -pipe
-Wl,-rpath=/usr/local/lib/gcc42 -c -o llvmunittest_JIT-JITTest.o `test
-f 'llvm/unittests/ExecutionEngine/JIT/JITTest.cpp' || echo
'./'`llvm/unittests/ExecutionEngine/JIT/JITTest.cpp
(Continue reading)

Török Edwin | 1 Mar 2010 21:41
Picon

Re: Tests failing on FreeBSD 6.x

On 03/01/2010 09:22 PM, Renato Botelho wrote:
> Hello one more time,
> 
> I was trying to update clamav-devel port to a more recent snapshot
> and I got some segfaults during make test, like you can see here:

Which FreeBSD version, and which architecture?

> 
> g++42: -rpath=/usr/local/lib/gcc42: linker input file unused because
> linking not done
>   CXX    llvmunittest_JIT-JITMemoryManagerTest.o
> g++42 -DHAVE_CONFIG_H -I.  -I./llvm/include -I./llvm/include
> -D__STDC_LIMIT_MACROS -D__STDC_CONSTANT_MACROS -D_DEBUG -D_GNU_SOURCE
> -I./llvm/utils/unittest/googletest/include -I/usr/local/include
> -Woverloaded-virtual -pedantic -Wno-long-long -Wall -W
> -Wno-unused-parameter -Wwrite-strings -Wno-missing-field-initializers
> -Wno-variadic-macros -fno-exceptions -O2 -fno-strict-aliasing -pipe
> -Wl,-rpath=/usr/local/lib/gcc42 -c -o
> llvmunittest_JIT-JITMemoryManagerTest.o `test -f
> 'llvm/unittests/ExecutionEngine/JIT/JITMemoryManagerTest.cpp' || echo
> './'`llvm/unittests/ExecutionEngine/JIT/JITMemoryManagerTest.cpp
> g++42: -rpath=/usr/local/lib/gcc42: linker input file unused because
> linking not done
>   CXX    llvmunittest_JIT-JITTest.o
> g++42 -DHAVE_CONFIG_H -I.  -I./llvm/include -I./llvm/include
> -D__STDC_LIMIT_MACROS -D__STDC_CONSTANT_MACROS -D_DEBUG -D_GNU_SOURCE
> -I./llvm/utils/unittest/googletest/include -I/usr/local/include
> -Woverloaded-virtual -pedantic -Wno-long-long -Wall -W
> -Wno-unused-parameter -Wwrite-strings -Wno-missing-field-initializers
(Continue reading)

Renato Botelho | 1 Mar 2010 21:46
Picon
Gravatar

Re: Tests failing on FreeBSD 6.x

2010/3/1 Török Edwin <edwintorok <at> gmail.com>:
> On 03/01/2010 09:22 PM, Renato Botelho wrote:
>> Hello one more time,
>>
>> I was trying to update clamav-devel port to a more recent snapshot
>> and I got some segfaults during make test, like you can see here:
>
> Which FreeBSD version, and which architecture?

6.4-RELEASE amd64

> Can you get a gdb backtrace for one of these? (when built with debug
> symbols)
> Just run gdb ./llvmunittest_ADT
> (gdb) run
> ...
> (gdb) bt

I don't have a real FreeBSD 6.4 machine around, I was testing it using
tinderbox [1], i'll read tinderbox documentation and see if there is a way
to stop the building without clean environment, so I can do it.

--

-- 
Renato Botelho
_______________________________________________
http://lurker.clamav.net/list/clamav-devel.html
Please submit your patches to our Bugzilla: http://bugs.clamav.net

Török Edwin | 1 Mar 2010 23:10
Picon

Re: Tests failing on FreeBSD 6.x

On 03/01/2010 10:46 PM, Renato Botelho wrote:
> 2010/3/1 Török Edwin <edwintorok <at> gmail.com>:
>> On 03/01/2010 09:22 PM, Renato Botelho wrote:
>>> Hello one more time,
>>>
>>> I was trying to update clamav-devel port to a more recent snapshot
>>> and I got some segfaults during make test, like you can see here:
>> Which FreeBSD version, and which architecture?
> 
> 6.4-RELEASE amd64

I have 6.4 i386 in a VM :(

I just installed gcc42 on it (pkg_add needed some convincing to use
packages-6-stable instead of packages-6.4-release), and llvmunittest_ADT
worked.

I did this:
./configure CXX=g++42 CC=gcc42 --disable-clamav --enable-llvm
cd libclamav/c++
make llvmunittest_ADT
./llvmunittest_ADT

It told me that 92 tests passed.

My guess is that something goes wrong during startup, the ADT test is
really simple and tehre isn't much that can segfault there.

> 
>> Can you get a gdb backtrace for one of these? (when built with debug
(Continue reading)

Renato Botelho | 2 Mar 2010 00:37
Picon
Gravatar

Re: Tests failing on FreeBSD 6.x

2010/3/1 Török Edwin <edwintorok <at> gmail.com>:
> On 03/01/2010 10:46 PM, Renato Botelho wrote:
>> 2010/3/1 Török Edwin <edwintorok <at> gmail.com>:
>>> On 03/01/2010 09:22 PM, Renato Botelho wrote:
>>>> Hello one more time,
>>>>
>>>> I was trying to update clamav-devel port to a more recent snapshot
>>>> and I got some segfaults during make test, like you can see here:
>>> Which FreeBSD version, and which architecture?
>>
>> 6.4-RELEASE amd64
>
> I have 6.4 i386 in a VM :(
>
> I just installed gcc42 on it (pkg_add needed some convincing to use
> packages-6-stable instead of packages-6.4-release), and llvmunittest_ADT
> worked.
>
> I did this:
> ./configure CXX=g++42 CC=gcc42 --disable-clamav --enable-llvm
> cd libclamav/c++
> make llvmunittest_ADT
> ./llvmunittest_ADT
>
> It told me that 92 tests passed.
>
> My guess is that something goes wrong during startup, the ADT test is
> really simple and tehre isn't much that can segfault there.
>
>>
(Continue reading)

Limor Tal | 2 Mar 2010 13:00
Picon

Do I really have to upgrade to 0.95 ?...

1. Can I keep using code that is older than 0.95 with the future CVD files
(those that will be distributed starting from May 2010) if I do not use
sigtool and cdiff?
2. Are those the only places in the code where the long signatures in the
daily file cause a problem?
3. Is the signature length the only incompatibility issue?
4. Can I choose to ignore the "special signature which disables all clamd
installations older than 0.95"?
_______________________________________________
http://lurker.clamav.net/list/clamav-devel.html
Please submit your patches to our Bugzilla: http://bugs.clamav.net

Török Edwin | 2 Mar 2010 13:42
Picon

Re: Do I really have to upgrade to 0.95 ?...

On 03/02/2010 02:00 PM, Limor Tal wrote:
> 1. Can I keep using code that is older than 0.95 with the future CVD files

Why? What prevents you from upgrading?
What version are you running now?

> (those that will be distributed starting from May 2010) if I do not use
> sigtool and cdiff?

If you somehow workaround the special signature (your question 4), then
the CVD will load. It may, or may not work; it may, or may not crash.

There is also bug #1331 (which got fixed in 0.95) affecting libclamav
with logical signatures.

All signatures can specify a "functionality level" to say what is the
minimum engine version needed to load them. When we release a signature
that makes use of these new features, we usually set the minimum
functionality level (so old engines will skip the signature).

However due to bug #1331, ClamAV <0.95 which tries to load a logical
signature with a functionality level specified, it will either read
uninitialized memory, or crash.
So even if we wanted to add functionality level to the new ldbs, so that
older engines (than 0.95) can load it, we can't since adding the
functionality level would cause a crash for them.
If we don't add the functionality level, libclamav won't crash, but will
probably fail to load the signature with a syntax error.

> 2. Are those the only places in the code where the long signatures in the
(Continue reading)

Brandon Perry | 2 Mar 2010 16:44
Picon
Gravatar

Re: Do I really have to upgrade to 0.95 ?...

I can understand that on some legacy production systems, it would be easier
to work around than upgrade. I have run into FC3 production machines, and
just compiling clamav or such wouldn't just work.

Limor, can you give us a reason why it's an issue?

2010/3/2 Török Edwin <edwintorok <at> gmail.com>

> On 03/02/2010 02:00 PM, Limor Tal wrote:
> > 1. Can I keep using code that is older than 0.95 with the future CVD
> files
>
> Why? What prevents you from upgrading?
> What version are you running now?
>
> > (those that will be distributed starting from May 2010) if I do not use
> > sigtool and cdiff?
>
> If you somehow workaround the special signature (your question 4), then
> the CVD will load. It may, or may not work; it may, or may not crash.
>
> There is also bug #1331 (which got fixed in 0.95) affecting libclamav
> with logical signatures.
>
> All signatures can specify a "functionality level" to say what is the
> minimum engine version needed to load them. When we release a signature
> that makes use of these new features, we usually set the minimum
> functionality level (so old engines will skip the signature).
>
> However due to bug #1331, ClamAV <0.95 which tries to load a logical
(Continue reading)

Matt Watchinski | 2 Mar 2010 19:18

ClamAV Community Announcement

The release date for ClamAV 0.96 RC 1 has been moved up to March 10th, 2010.
With that in mind, I wanted to take a moment to highlight some of the new
features we've been working on and a new product for ClamAV Windows users.
Additionally, I'd like to encourage users to try out the RC when its released on
March 10th to help us find bugs before the final release.

First up, let's talk about 0.96 and some of its major new features.

1. The Bytecode Interpreter - The Bytecode Interpreter allows ClamAV sig-makers
to create very complex AV signatures for complex pieces of malware.  This is a
pretty major addition to the detection technologies inside of ClamAV.

2. Native Windows Support - ClamAV will now build natively under Visual Studio.
This will allow 3rd Party application developers on windows to easily integrate
LibClamAV into their applications.

3. UPX 3.0 unpacking support - Add support to decompressing UPX version 3.0
packed applications.

4. 7zip archive support - Add support for decompressing 7zip archives and
inspecting their contents.

5. OSX Mach-O support - Add support for parsing OSX Mach-O binaries files and
intelligently inspecting their contents

6. 64-bit ELF support - Add support for intelligently parsing and detecting
malware in 64-Bit ELF binaries.

7. InstallShield archives support - Add support for unpacking and inspecting the
contents of InstallShield archives.
(Continue reading)

Brandon Perry | 2 Mar 2010 19:27
Picon
Gravatar

ClamAV Community Announcement

This is awesome. You guys rock hardcore.

On Mar 2, 2010 12:24 PM, "Matt Watchinski" <mwatchinski <at> sourcefire.com>
wrote:

The release date for ClamAV 0.96 RC 1 has been moved up to March 10th, 2010.
With that in mind, I wanted to take a moment to highlight some of the new
features we've been working on and a new product for ClamAV Windows users.
Additionally, I'd like to encourage users to try out the RC when its
released on
March 10th to help us find bugs before the final release.

First up, let's talk about 0.96 and some of its major new features.

1. The Bytecode Interpreter - The Bytecode Interpreter allows ClamAV
sig-makers
to create very complex AV signatures for complex pieces of malware.  This is
a
pretty major addition to the detection technologies inside of ClamAV.

2. Native Windows Support - ClamAV will now build natively under Visual
Studio.
This will allow 3rd Party application developers on windows to easily
integrate
LibClamAV into their applications.

3. UPX 3.0 unpacking support - Add support to decompressing UPX version 3.0
packed applications.

4. 7zip archive support - Add support for decompressing 7zip archives and
(Continue reading)


Gmane