Issues with my build process / openvas segmentation fault

You need to install the sources as well, to see where the process crashes.

Ah! Now I understand … ‘gdb’ is reporting the file not found because it’s trying to display line 1343 from “gthread-posix.c”

Unfortunately, I still have no idea what to do with this information. :frowning:

(gdb) run 
Starting program: /usr/local/sbin/openvas 
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/".

Program received signal SIGSEGV, Segmentation fault.
0x00007ffff7e9b005 in g_mutex_lock (mutex=0x0) at ../../../glib/gthread-posix.c:1343
1343      if G_UNLIKELY (g_atomic_int_add (&mutex->i[0], 1) != 0)
(gdb) bt
#0  0x00007ffff7e9b005 in g_mutex_lock (mutex=0x0) at ../../../glib/gthread-posix.c:1343
#1  0x0000555555560595 in create_process (function=function@entry=0x55555555e9c0 <plugins_reload_from_dir>, argument=argument@entry=0x5555555a16b0)
    at /build/openvas-scanner-21.4.3/src/processes.c:102
#2  0x000055555555f058 in plugins_init () at /build/openvas-scanner-21.4.3/src/pluginload.c:391
#3  0x000055555555dc86 in openvas (argc=<optimized out>, argv=<optimized out>) at /build/openvas-scanner-21.4.3/src/openvas.c:591
#4  0x00007ffff678d09b in __libc_start_main (main=
    0x555555559b90 <main>, argc=1, argv=0x7fffffffecf8, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7fffffffece8) at ../csu/libc-start.c:308
#5  0x0000555555559bca in _start ()

Anyone interested in looking at this, since it’s running in a container, I exported the whole thing with gdb, dbg-sym, and source already setup. Fair warning though, it is HUGE. 6Gb on docker and 14GB decompressed.

docker pull immauss/openvas:debug

1 Like

Thanks to @Raphael, I now know that if we build gvm-libs & openvas-scanner from the stable branch, that it works fine.

@bricks any idea what changed?

Circling back on the chance anyone was waiting for answer here. This was due to a missing openvas_log.conf .
Details here:

1 Like