how to report crash recorded with gdb

Neal Becker ndbecker2 at gmail.com
Sat Feb 25 15:35:29 UTC 2023


"where" should give a traceback

On Sat, Feb 25, 2023, 9:01 AM Wolfgang Engelmann <engelmann at uni-tuebingen.de>
wrote:

> I ran a lyx document under 2.4 which was started with gdb. It crashed
> and I do not know how to report it to the maintainers. This is the
> terminal >
>
> text-user-interface -- TUI is the GDB text based interface.
> tracepoints -- Tracing of program execution without stopping the program.
> user-defined -- User-defined commands.
>
> Type "help" followed by a class name for a list of commands in
> that class.
> Type "help all" for the list of all commands.
> Type "help" followed by command name for full documentation.
> Type "apropos word" to search for commands related to "word".
> Type "apropos -v word" for full documentation
>   of commands related to "word".
> Command name abbreviations are allowed if unambiguous.
> (gdb) q
> A debugging session is active.
>
>          Inferior 1 [process 2797] will be killed.
>
> Quit anyway? (y or n) n
> Not confirmed.
> (gdb)
>
> It is still running, so if you or somebody else could tell me what to do
> to report it.
>
> Wolfgang
> --
> lyx-users mailing list
> lyx-users at lists.lyx.org
> http://lists.lyx.org/mailman/listinfo/lyx-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lyx.org/pipermail/lyx-users/attachments/20230225/4d3e4ee0/attachment.html>


More information about the lyx-users mailing list