Re: getting proper debug information

[pin <voidpin%protonmail.com@localhost>]

On Friday, February 7th, 2025 at 3:15 PM, Martin Husemann <martin%duskware.de@localhost> wrote:

> 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

Thank you!
But ...

gdb -ex=r --args inlyne view README.md
GNU gdb (GDB) 15.1
Copyright (C) 2024 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "x86_64--netbsd".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<https://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
    <http://www.gnu.org/software/gdb/documentation/>.

For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from inlyne...
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.
Starting program: /usr/local/bin/inlyne view README.md
/usr/src/external/gpl3/gdb/lib/libgdb/../../dist/gdb/thread.c:1423: internal-error: switch_to_thread: Assertion `thr != NULL' failed.
A problem internal to GDB has been detected,
further debugging may prove unreliable.
----- Backtrace -----
0x4fcbdb _Z22gdb_internal_backtracev
0x3bff07 _ZL17internal_vproblemP16internal_problemPKciS2_P13__va_list_tag
0x3c0237 _Z15internal_verrorPKciS0_P13__va_list_tag
0x7d9c27 _Z18internal_error_locPKciS0_z
0x3e89b7 _Z16switch_to_threadP11thread_info.part.0
0x3ea5f5 _Z16switch_to_threadP22process_stratum_target6ptid_t
0x6c94db _Z16startup_inferiorP22process_stratum_targetiiP17target_waitstatusP6ptid_t
0x6ca6e6 _Z20gdb_startup_inferiorii
0x64e376 _ZN17inf_ptrace_target15create_inferiorEPKcRKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEEPPci
0x4c8306 _ZL13run_command_1PKci7run_how
0x6184d5 _Z8cmd_funcP16cmd_list_elementPKci
0x3e7a7a _Z15execute_commandPKci
0x47c6fd _ZL20catch_command_errorsPFvPKciES0_ib
0x47c7c4 _ZL15execute_cmdargsPKSt6vectorI6cmdargSaIS0_EE11cmdarg_kindS5_Pi
0x47e7ba _ZL15captured_main_1P18captured_main_args
0x47f1f2 _Z8gdb_mainP18captured_main_args
0x8b91d7 main
---------------------
/usr/src/external/gpl3/gdb/lib/libgdb/../../dist/gdb/thread.c:1423: internal-error: switch_to_thread: Assertion `thr != NULL' failed.
A problem internal to GDB has been detected,
further debugging may prove unreliable.
Quit this debugging session? (y or n) y

How exactly should I launch it?
Sorry.