On Thu, 13 Jun 2024 20:24:33 +0800 =?UTF-8?B?RGFuYWkgU0FFLUhBTiAo6Z+T6YGU6ICQKQ==?=
<da...@debian.org> wrote:
==659486== Process terminating with default action of signal 11 (SIGSEGV)
==659486== Access not within mapped region at address 0x0
==659486== at 0x4847DC4: strcmp (in
/usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so)
==659486== by 0x11D8A5: ??? (in /usr/bin/cyanrip)
==659486== by 0x10F57C: ??? (in /usr/bin/cyanrip)
==659486== by 0x8100C89: (below main) (libc_start_call_main.h:58)
Thread 1 "cyanrip" received signal SIGSEGV, Segmentation fault.
(gdb) bt
#0 __strcmp_avx2 () at ../sysdeps/x86_64/multiarch/strcmp-avx2.S:283
#1 0x00005555555698b6 in ()
#2 0x000055555555b585 in ()
#3 0x00007ffff4442c8a in __libc_start_call_main
(main=main@entry=0x555555559f20, argc=argc@entry=9,
argv=argv@entry=0x7fffffffdbd8) at ../sysdeps/nptl/libc_start_call_main.h:58
#4 0x00007ffff4442d45 in __libc_start_main_impl (main=0x555555559f20, argc=9,
argv=0x7fffffffdbd8, init=<optimized out>, fini=<optimized out>,
rtld_fini=<optimized out>, stack_end=0x7fffffffdbc8) at ../csu/libc-start.c:360
#5 0x000055555555d131 in ()
Hello Danai,
the lines at 0x555555... are in the main executable and unfortunately your
gdb could not locate the debug symbols.
Therefore a first step would be to get these, then debuggers
should be able to show source line information.
This page lists a few ways: https://wiki.debian.org/HowToGetABacktrace
I find it nice to add the debug repository and install
the dbgsym packages as needed, in this case cyanrip-dbgsym.
The DEBUGINFOD_URLS method is easier, but may take longer because it downloads
everything for the debugged process and creates a cache directory in HOME.
Kind regards,
Bernhard
