From: "Gerd Möllmann" <gerd.moellmann@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: luangruo@yahoo.com, 56095@debbugs.gnu.org
Subject: bug#56095: 29.0.50; nsterm.m, use after free
Date: Wed, 22 Jun 2022 15:43:09 +0200 [thread overview]
Message-ID: <a1930ca7-3e3e-4acc-a00a-0b7f86ee31cb@Spark> (raw)
In-Reply-To: <83edzgkf4p.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 636 bytes --]
On 22. Jun 2022, 15:21 +0200, Eli Zaretskii <eliz@gnu.org>, wrote:
> >
> > Ah, that platform is not even supported...
> >
> > Unfortunately, using LLDB for debugging Emacs means you won't be able
> > to use the commands defined in src/.gdbinit, which makes examining
> > Lisp data very inconvenient, to say the least.
Yeah, to say the least :-).
> > Unless, that is, you
> > or someone else rewrites those commands in some script LLDB supports;
> > no one has done that yet, AFAIK.
Looks like that. I couldn't find anything on the web either.
I see LDB has Python scripting. Maybe it's not so hard after all, then.
[-- Attachment #2: Type: text/html, Size: 1543 bytes --]
next prev parent reply other threads:[~2022-06-22 13:43 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-19 14:28 bug#56095: 29.0.50; nsterm.m, use after free Gerd Möllmann
2022-06-20 1:22 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-06-20 6:02 ` Gerd Möllmann
2022-06-20 10:21 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-06-21 14:25 ` Gerd Möllmann
2022-06-21 15:43 ` Eli Zaretskii
2022-06-22 5:26 ` Gerd Möllmann
2022-06-22 9:19 ` Gerd Möllmann
2022-06-22 13:21 ` Eli Zaretskii
2022-06-22 13:43 ` Gerd Möllmann [this message]
2022-06-22 1:30 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-06-22 13:53 ` Eli Zaretskii
2022-06-22 14:15 ` Gerd Möllmann
2022-06-22 16:14 ` Eli Zaretskii
[not found] <27290ad8-4f51-41e5-9317-46e4b3c5dd6c@Spark>
2022-06-19 17:32 ` bug#56095: Patch Gerd Möllmann
2022-06-19 22:51 ` bug#56095: 29.0.50; nsterm.m, use after free Lars Ingebrigtsen
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=a1930ca7-3e3e-4acc-a00a-0b7f86ee31cb@Spark \
--to=gerd.moellmann@gmail.com \
--cc=56095@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=luangruo@yahoo.com \
/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.