[minicoredumper] gdb corrupt stack
Marco.Felsch at preh.de
Marco.Felsch at preh.de
Mon Jul 3 17:06:39 CEST 2017
Hi,
I had cross compiled the minicoredumper for the aarch64.
Generating the core file works fine but analyze the the core file with gdb on a remote host isn't possible.
I only want a small core file to show the backtrace within gdb.
I am able to show the top most (#0/#1) backtrace entries but no more.
My setup was:
- cross compiler: gcc-linaro-6.2.1-2016.11-x86_64_aarch64-linux-gnu
- cross compiled elfutils-0.169, and json-c lib
- my gdb sysroot contains all the libraries and the executable
Maybe I forgot to set a specific configuration?
You will find the generic.recept and the gdb output attached.
My config file:
{
"stacks": {
"dump_stacks": true,
"first_thread_only": false,
"max_stack_size": 0
},
"maps": {
"dump_by_name": [
"[vdso]"
]
},
"compression": {
"compressor": "gzip",
"extension": "gz",
"in_tar": true
},
"dump_auxv_so_list": true,
"dump_pthread_list": true,
"dump_robust_mutex_list": true,
"live_dumper": false,
"write_proc_info": false,
"write_debug_log": false,
"dump_fat_core": true
}
gdb-output:
[New LWP 4323]
Core was generated by `htop'.
Program terminated with signal SIGABRT, Aborted.
#0 0x0000007f816a3168 in __GI_raise (sig=sig at entry=6) at ../sysdeps/unix/sysv/linux/raise.c:54
54 ../sysdeps/unix/sysv/linux/raise.c: No such file or directory.
(gdb) bt
#0 0x0000007f816a3168 in __GI_raise (sig=sig at entry=6) at ../sysdeps/unix/sysv/linux/raise.c:54
#1 0x0000007f816a455c in __GI_abort () at abort.c:89
#2 0x0000000000000000 in ?? ()
Backtrace stopped: previous frame identical to this frame (corrupt stack?)
More information about the minicoredumper
mailing list