From: "Gerd Möllmann" <gerd.moellmann@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: pipcet@protonmail.com, telegraph@gmx.net, 75459@debbugs.gnu.org
Subject: 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
Date: Fri, 10 Jan 2025 09:14:53 +0100 [thread overview]
Message-ID: <m2ikqnxeyq.fsf@gmail.com> (raw)
In-Reply-To: <86ikqn14wo.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 10 Jan 2025 09:53:11 +0200")
Eli Zaretskii <eliz@gnu.org> writes:
>
> ...the above makes me wonder whether calling this unconditionally will
> shoot us in the foot. Debugging with GDB does sometimes call
> functions in the debuggee, whereas the above says "no longer safe to
> continue running the client program". I wonder what kind of
> "postmortem debugging" they had in mind, perhaps only debugging
> MPS-related code itself?
I've had a number of cases where barriers got in the way of looking
around in the Lisp data using LLDB. Say one starts with a list, some car
is a symbol, and one looks at the value of the symbol. Something like
that.
It's not ideal that MPS is dead after xpostmortem, but better than
nothing.
next prev parent reply other threads:[~2025-01-10 8:14 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-09 11:19 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 Gregor Zattler via Bug reports for GNU Emacs, the Swiss army knife of text editors
2025-01-09 13:03 ` Eli Zaretskii
2025-01-09 14:34 ` Gerd Möllmann
2025-01-09 14:47 ` Pip Cet via Bug reports for GNU Emacs, the Swiss army knife of text editors
2025-01-09 15:32 ` Gregor Zattler via Bug reports for GNU Emacs, the Swiss army knife of text editors
2025-01-09 16:14 ` Gerd Möllmann
2025-01-09 19:27 ` Pip Cet via Bug reports for GNU Emacs, the Swiss army knife of text editors
2025-01-09 22:29 ` Gregor Zattler via Bug reports for GNU Emacs, the Swiss army knife of text editors
2025-01-10 13:59 ` Pip Cet via Bug reports for GNU Emacs, the Swiss army knife of text editors
2025-01-10 4:52 ` Gerd Möllmann
2025-01-10 7:15 ` Eli Zaretskii
2025-01-10 7:29 ` Gerd Möllmann
2025-01-10 7:53 ` Eli Zaretskii
2025-01-10 8:14 ` Gerd Möllmann [this message]
2025-01-10 13:46 ` Pip Cet via Bug reports for GNU Emacs, the Swiss army knife of text editors
2025-01-10 14:27 ` Gerd Möllmann
2025-01-10 14:46 ` Pip Cet via Bug reports for GNU Emacs, the Swiss army knife of text editors
2025-01-10 15:27 ` Gerd Möllmann
2025-01-10 14:44 ` Eli Zaretskii
2025-01-10 15:30 ` Pip Cet via Bug reports for GNU Emacs, the Swiss army knife of text editors
2025-01-10 18:56 ` Eli Zaretskii
2025-01-09 14:52 ` Gerd Möllmann
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m2ikqnxeyq.fsf@gmail.com \
--to=gerd.moellmann@gmail.com \
--cc=75459@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=pipcet@protonmail.com \
--cc=telegraph@gmx.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).