From: "Gerd Möllmann" <gerd.moellmann@gmail.com>
To: Pip Cet <pipcet@protonmail.com>
Cc: Eli Zaretskii <eliz@gnu.org>, 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 15:27:36 +0100 [thread overview]
Message-ID: <m25xmmyc9z.fsf@gmail.com> (raw)
In-Reply-To: <87ldvi3hok.fsf@protonmail.com> (Pip Cet's message of "Fri, 10 Jan 2025 13:46:40 +0000")
Pip Cet <pipcet@protonmail.com> writes:
> Gerd Möllmann <gerd.moellmann@gmail.com> writes:
>
>> Ah, that explains it, thanks! Didn't know about that hook.
>
> That explains why "backtrace" doesn't show up; it doesn't explain why
> backtrace_function asserts on data that we previously ensured would be of
> the right kind.
True.
>> I call that command manually when MPS gets in the way. Here is the
>
> Does lldb allow you to inspect memory that is behind a barrier?
No, or at least I don't know how I could do that.
(LLDB's Python API, which I use, is a SWIG wrapper of the C++ objects the
lldb lib uses. The Python classes are not completely documented, so
there might be something hidden somewhere.)
next prev parent reply other threads:[~2025-01-10 14:27 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
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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m25xmmyc9z.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.