Re: getting proper debug information

[Martin Husemann <martin%duskware.de@localhost>]

On Fri, Feb 07, 2025 at 02:08:49PM +0000, pin wrote:
> Core was generated by `inlyne'.
> Program terminated with signal SIGSEGV, Segmentation fault.
> #0  0x0000700e45ffeba7 in ?? ()
> [Current thread is 1 (process 6059)]
> warning: Unsupported auto-load script at offset 0 in section .debug_gdb_scripts
> of file /usr/local/bin/inlyne.
> Use `info auto-load python-scripts [REGEXP]' to list them.
> (gdb) bt
> #0  0x0000700e45ffeba7 in ?? ()
> #1  0x0000700e485186ad in ?? ()
> #2  0x0000700e482ec220 in ?? ()
> #3  0x0000000000000000 in ?? ()
> 
> How do I get a proper backtrace that I can use?

You often get better results from gdb if you use gdb to run the program.
This will disable ASLR and gdb will know the shared library mappings in
effect when the crash happens.

Martin