Segmentation fault upon a startup

[JohnyRi]

Hi,
after building the last version on Arch Linux I am not able to start the Hybrid due to segmentation fault immediately after startup.
Unfortunately, I am not able to get any debug or info whatsoever except this:

$ Hybrid
Segmentation fault (core dumped)

The output from the journal:

systemd-coredump[207125]: Process 207123 (Hybrid) of user 1000 dumped core.
            
                                                      Stack trace of thread 207123:
                                                      #0  0x00007fa7711e1100 n/a (n/a + 0x0)

I also tried to run Hybrid with valgrind to get more debug info:

$ valgrind -v Hybrid
==92525== Memcheck, a memory error detector
==92525== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al.
==92525== Using Valgrind-3.15.0-608cb11914-20190413X and LibVEX; rerun with -h for copyright info
==92525== Command: Hybrid
==92525==
--92525-- Valgrind options:
--92525--    -v
--92525-- Contents of /proc/version:
--92525--  Linux version 5.6.10-arch1-1 (linux@archlinux) (gcc version 9.3.0 (Arch Linux 9.3.0-1)) #1 SMP PREEMPT Sat, 02 May 2020 19:11:54 +0000
--92525--
--92525-- Arch and hwcaps: AMD64, LittleEndian, amd64-cx16-lzcnt-rdtscp-sse3-ssse3-avx-avx2-bmi-f16c-rdrand
--92525-- Page sizes: currently 4096, max supported 4096
--92525-- Valgrind library directory: /usr/lib/valgrind
--92525-- Reading syms from /usr/lib/valgrind/memcheck-amd64-linux
--92525--    object doesn't have a dynamic symbol table
--92525-- Scheduler: using generic scheduler lock implementation.
--92525-- Reading suppressions file: /usr/lib/valgrind/default.supp
==92525== embedded gdbserver: reading from /tmp/vgdb-pipe-from-vgdb-to-92525-by-johnyr-on-???
==92525== embedded gdbserver: writing to  /tmp/vgdb-pipe-to-vgdb-from-92525-by-johnyr-on-???
==92525== embedded gdbserver: shared mem  /tmp/vgdb-pipe-shared-mem-vgdb-92525-by-johnyr-on-???
==92525==
==92525== TO CONTROL THIS PROCESS USING vgdb (which you probably
==92525== don't want to do, unless you know exactly what you're doing,
==92525== or are doing some strange experiment):
==92525==  /usr/lib/valgrind/../../bin/vgdb --pid=92525 ...command...
==92525==
==92525== TO DEBUG THIS PROCESS USING GDB: start GDB like this
==92525==  /path/to/gdb Hybrid
==92525== and then give GDB the following command
==92525==  target remote | /usr/lib/valgrind/../../bin/vgdb --pid=92525
==92525== --pid is optional if only one valgrind process is running
==92525==
--92525-- Reading syms from /usr/lib/ld-2.31.so
--92525-- REDIR: 0x69c82b0 (ld-linux-x86-64.so.2:strlen) redirected to 0x580c7532 (vgPlain_amd64_linux_REDIR_FOR_strlen)
==92525== Invalid read of size 4
==92525==    at 0x69AABEE: dl_main (in /usr/lib/ld-2.31.so)
==92525==    by 0x69C225A: _dl_sysdep_start (in /usr/lib/ld-2.31.so)
==92525==    by 0x69A9FDB: _dl_start (in /usr/lib/ld-2.31.so)
==92525==    by 0x69A9107: ??? (in /usr/lib/ld-2.31.so)
==92525==  Address 0x208040 is not stack'd, malloc'd or (recently) free'd
==92525==
==92525==
==92525== Process terminating with default action of signal 11 (SIGSEGV): dumping core
==92525==  Access not within mapped region at address 0x208040
==92525==    at 0x69AABEE: dl_main (in /usr/lib/ld-2.31.so)
==92525==    by 0x69C225A: _dl_sysdep_start (in /usr/lib/ld-2.31.so)
==92525==    by 0x69A9FDB: _dl_start (in /usr/lib/ld-2.31.so)
==92525==    by 0x69A9107: ??? (in /usr/lib/ld-2.31.so)
==92525==  If you believe this happened as a result of a stack
==92525==  overflow in your program's main thread (unlikely but
==92525==  possible), you can try to increase the size of the
==92525==  main thread stack using the --main-stacksize= flag.
==92525==  The main thread stack size used in this run was 8388608.
==92525==
==92525== HEAP SUMMARY:
==92525==    in use at exit: 0 bytes in 0 blocks
==92525==  total heap usage: 0 allocs, 0 frees, 0 bytes allocated
==92525==
==92525== All heap blocks were freed -- no leaks are possible
==92525==
==92525== ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 0 from 0)
==92525==
==92525== 1 errors in context 1 of 1:
==92525== Invalid read of size 4
==92525==    at 0x69AABEE: dl_main (in /usr/lib/ld-2.31.so)
==92525==    by 0x69C225A: _dl_sysdep_start (in /usr/lib/ld-2.31.so)
==92525==    by 0x69A9FDB: _dl_start (in /usr/lib/ld-2.31.so)
==92525==    by 0x69A9107: ??? (in /usr/lib/ld-2.31.so)
==92525==  Address 0x208040 is not stack'd, malloc'd or (recently) free'd
==92525==
==92525== ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 0 from 0)
Segmentation fault (core dumped)

Could you please point me to some way I could debug better and discover what could be the issue?
Thanx,
Jan