Ubuntu
clamav package

  1. Bug #1717574
  2. Comment #17

Comment 17 for bug 1717574

Revision history for this message
Christian Ehrhardt  (paelzer) wrote : Re: freshclam crashed with SIGABRT in __assert_fail_base()

I was working on rebuilds:
- new clamav for zesty
- rebuild of new clamav on artful
- unittests local in lxd containers

It turns out that it is no more building in artful (but still in zesty).
But it all matches our current assumptions, as also this is on bytecode execution.

FAIL: check_clamav
==================

Using test case timeout of 900 seconds set by user
Running suite(s): cl_api
 cli
 jsnorm
 str
 regex
 disasm
 unique
 matchers
 htmlnorm
 bytecode
98%: Checks: 964, Failures: 0, Errors: 12
check_bytecode.c:93:E:arithmetic:test_lsig_jit:0: (after this point) Received signal 6 (Aborted)
check_bytecode.c:93:E:arithmetic:test_matchwithread_jit:0: (after this point) Received signal 6 (Aborted)
check_bytecode.c:93:E:arithmetic:test_pdf_jit:0: (after this point) Received signal 6 (Aborted)
check_bytecode.c:93:E:arithmetic:test_bswap_jit:0: (after this point) Received signal 6 (Aborted)
check_bytecode.c:93:E:arithmetic:test_inflate_int:0: (after this point) Received signal 6 (Aborted)
check_bytecode.c:93:E:arithmetic:test_api_files_jit:0: (after this point) Received signal 6 (Aborted)
check_bytecode.c:93:E:arithmetic:test_arith_7_jit:0: (after this point) Received signal 6 (Aborted)
check_bytecode.c:93:E:arithmetic:test_debug_jit:0: (after this point) Received signal 6 (Aborted)
check_bytecode.c:93:E:arithmetic:test_lsig_7_jit:0: (after this point) Received signal 6 (Aborted)
check_bytecode.c:93:E:arithmetic:test_testadt_jit:0: (after this point) Received signal 6 (Aborted)
check_bytecode.c:496:E:arithmetic:test_load_bytecode_jit:0: (after this point) Received signal 6 (Aborted)
check_bytecode.c:496:E:arithmetic:test_parallel_load:0: (after this point) Received signal 6 (Aborted)
NOTICE: Use the 'T' environment variable to adjust testcase timeout
FAIL check_clamav (exit status: 1)

Now on the "rebuild" we have to consider that the bytecode.cvd in the test is part of the package, and the one failing in the real system is downloaded.
If there are toolchain ABI breaks (which should not happen) then the incompatibility might be between what clamac builds their bytecode.cvd with vs the one now in Ubuntu.