GNU bug report logs - #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

Previous Next

Full log

View this message in rfc822 format

From: Eli Zaretskii <eliz <at> gnu.org>
To: Pip Cet <pipcet <at> protonmail.com>
Cc: gerd.moellmann <at> gmail.com, telegraph <at> gmx.net, 75459 <at> debbugs.gnu.org
Subject: bug#75459: 31.0.50; scratch-igc: Breakpoint 1, terminate_due_to_signal (sig=sig <at> entry=6, backtrace_limit=backtrace_limit <at> entry=2147483647) at ./src/emacs.c:432
Date: Fri, 10 Jan 2025 16:44:54 +0200

> Date: Fri, 10 Jan 2025 13:46:40 +0000
> From: Pip Cet <pipcet <at> protonmail.com>
> Cc: Eli Zaretskii <eliz <at> gnu.org>, telegraph <at> gmx.net, 75459 <at> 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.)

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.