bug#75459: 31.0.50; scratch-igc: Breakpoint 1, terminate_due_to_signal (sig=sig@entry=6, backtrace_limit=backtrace_limit@entry=2147483647) at ./src/emacs.c:432

[Eli Zaretskii <eliz@gnu.org>]

> Date: Fri, 10 Jan 2025 13:46:40 +0000
> From: Pip Cet <pipcet@protonmail.com>
> Cc: Eli Zaretskii <eliz@gnu.org>, telegraph@gmx.net, 75459@debbugs.gnu.org
> 
> If calling backtrace in GDB means we can't continue afterwards, that
> would be very bad.  I think it's already bad that we automatically
> append the Lisp backtrace to "bt" output.  IMHO, "bt" should limit
> itself to accessing process memory via PTRACE, not call into application
> code.  Making it destroy the Emacs session even when we can get a
> backtrace would be worse.

Usually, automatically calling xbacktrace is very useful.  In cases
where it is not, one can disable it, like this:

  (gdb)  define hookpost-backtrace
  Redefine command "hookpost-backtrace"? (y or n) y
  Type commands for definition of "hookpost-backtrace".
  End with a line saying just "end".
  >end
  (gdb)

(It is also possible to start GDB from a directory other than the
Emacs src directory, but then one loses the other conveniencies of our
.gdbinit.)