Hello Jan,
Am 20.09.22 um 10:24 schrieb Jan Korbel:
1.
(gdb) bt
#0 __kernel_vsyscall ()
at
/build/linux-q1ABpl/linux-5.10.136/arch/x86/entry/vdso/vdso32/system_call.S:72
#1 0xf7695333 in fstab_init (opt_rewind=0) at fstab.c:121
2.
(gdb) bt
#0 __kernel_vsyscall ()
at
/build/linux-q1ABpl/linux-5.10.136/arch/x86/entry/vdso/vdso32/system_call.S:72
#1 0xf756ee02 in mrand48 () at mrand48.c:24
#2 0xf3f2c118 in ?? ()
3.
(gdb) bt
#0 __kernel_vsyscall ()
at
/build/linux-q1ABpl/linux-5.10.136/arch/x86/entry/vdso/vdso32/system_call.S:72
#1 0xf7564e02 in mrand48 () at mrand48.c:24
#2 0xf3efcd40 in ?? ()
4.
(gdb) bt
#0 __kernel_vsyscall ()
at
/build/linux-q1ABpl/linux-5.10.136/arch/x86/entry/vdso/vdso32/system_call.S:72
#1 0xf75a9e02 in mrand48 () at mrand48.c:24
#2 0x00000004 in ?? ()
Maybe you could backtraces with better/more information by having the
dbgsym packages installed, or calling gdb with the DEBUGINFOD_URLS from [10].
Is this some kind of virtualisation?
Does this also happen with a regular amd64- or i386-kernel?
Kind regards,
Bernhard
[10]
https://wiki.debian.org/HowToGetABacktrace#Automatically_loading_debugging_symbol_from_the_Internet
