bug#68755: 29.2; Emacs crashes repeatedly after some steps

[Eli Zaretskii <eliz@gnu.org>]

[Please use Reply All to reply, to keep the bug tracker CC'ed.]

> Date: Sat, 27 Jan 2024 14:08:40 +0100
> From: Ľuboš Pinteš <lubos.pintes@gmail.com>
> 
> Hello,
> 
> It is very difficult. If I attach the debugger, whole system seems to be 
> very unresponsive, at least from screen reader's point of view.
> 
> Can you provide me more details about how to do it?

Yes:

  . start Emacs from a Command prompt window like this:

      gdb emacs

  . this will show the GDB prompt "(gdb)".  Type "run" (without the
    quotes) to run Emacs under GDB.

  . when Emacs starts up, do whatever you need to cause Emacs crash

  . when Emacs crashes, you will see the "(gdb)" prompt in the Command
    prompt window where you started Emacs under GDB.  Type at that
    prompt:

      thread apply all bt

  . GDB will show the backtrace; copy/paste it into your email reply
    to this message, and send your email rely

> If I don't bother with the debugger, and press "No" button in the 
> messagebox that pops up a "emacs_backtrace.txt" is generated.
> 
> Is that sufficient? If not then I need more information about capturing 
> the backtrace.

The file emacs_backtrace.txt can only be interpreted on your system,
since the program which converts the addresses to file names and
function names needs to read the emacs.exe file on your system.  So it
is much less useful for us than a backtrace generated by GDB.