Mailinglist Archive: opensuse-bugs (4751 mails)

< Previous Next >
[Bug 1041201] GCC 7: clamav fails to build
  • From: bugzilla_noreply@xxxxxxxxxx
  • Date: Tue, 04 Jul 2017 11:49:42 +0000
  • Message-id: <bug-1041201-21960-i8kesoo5VK@http.bugzilla.suse.com/>
http://bugzilla.suse.com/show_bug.cgi?id=1041201
http://bugzilla.suse.com/show_bug.cgi?id=1041201#c1

--- Comment #1 from Reinhard Max <max@xxxxxxxx> ---
It is a segfault in a binary that is part of the testsuite, not in ClamAV
itself:

--- snip (unit_tests/test-suite.log) ---
99%: Checks: 988, Failures: 1, Errors: 1
check_bytecode.c:127:F:arithmetic:test_inflate_jit:0: cli_bytecode_run failed,
expected: 0, have: 28

check_bytecode.c:108:E:arithmetic:test_inflate_int:0: (after this point)
Received signal 11 (Segmentation fault)
--- snap ---

I tried to debug the core dump, but even after installing all debuginfo
packages that gdb requested and making sure I have a binary with debug symbols,
I don't get any useful (for me) information:

--- snip ---
Reading symbols from
/home/abuild/rpmbuild/BUILD/clamav-0.99.2/unit_tests/.libs/check_clamav...done.
[New LWP 30499]
[New LWP 30500]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
Core was generated by
`/home/abuild/rpmbuild/BUILD/clamav-0.99.2/unit_tests/.libs/check_clamav'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0 0x00007f8f0fc8d13d in ?? ()
[Current thread is 1 (Thread 0x7f8f137f6b80 (LWP 30499))]
(gdb) bt
#0 0x00007f8f0fc8d13d in ?? ()
#1 0x00007ffff7f4faf0 in ?? ()
#2 0x0000000000000000 in ?? ()
(gdb) thread 2
[Switching to thread 2 (Thread 0x7f8f0fc8c700 (LWP 30500))]
#0 clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:80
80 ../sysdeps/unix/sysv/linux/x86_64/clone.S: No such file or directory.
(gdb) bt
#0 clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:80
#1 0x00007f8f123e8410 in ?? () at pthread_create.c:353 from
/lib64/libpthread.so.0
#2 0x00007f8f0fc8c700 in ?? ()
#3 0x0000000000000000 in ?? ()
--- snap ---

--
You are receiving this mail because:
You are on the CC list for the bug.
< Previous Next >