unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Yuan Fu <casouri@gmail.com>
To: Alan Third <alan@idiocy.org>
Cc: emacs-devel <emacs-devel@gnu.org>
Subject: Re: Debugging Emacs with lldb
Date: Fri, 23 Jul 2021 20:34:47 -0400	[thread overview]
Message-ID: <64C17491-439E-4538-9398-DA9DB0BB850E@gmail.com> (raw)
In-Reply-To: <YPtX3iTRafU+PyDO@idiocy.org>

[-- Attachment #1: Type: text/plain, Size: 1172 bytes --]



> On Jul 23, 2021, at 7:59 PM, Alan Third <alan@idiocy.org> wrote:
> 
> On Fri, Jul 23, 2021 at 07:50:21PM -0400, Yuan Fu wrote:
>> Hey Alan,
>> 
>> IIRC you are using lldb to debug Emacs. I’m stuck on a Mac and now
>> need to debug Emacs, too. lldb doesn’t get any of the commands
>> defined in gdbinit. How did you work around that? For example, how
>> do you check the lisp backtrace without xbacktrace? Right now I’m
>> staring at a wall of Ffuncall and don’t know what to do with it.
>> TIA.
> 
> I don't do much lisp work, so I've never really run up against these
> problems.
> 
> If you can get GDB installed it should be possible to sign it so it
> works. At least it used to be possible to do so. There are
> instructions on the internet, but I won't recommend any particular
> ones as I haven't done it for years.

I’ve tried countless times since 2019, and I can install and code sign GDB, but every time I “run”, gdb hangs. That seems to be a bug that was yet to be fixed[1]. 

Anyway, thanks!

[1]: https://sourceware.org/bugzilla/show_bug.cgi?id=24069 <https://sourceware.org/bugzilla/show_bug.cgi?id=24069>

Yuan

[-- Attachment #2: Type: text/html, Size: 1996 bytes --]

  reply	other threads:[~2021-07-24  0:34 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-23 23:50 Debugging Emacs with lldb Yuan Fu
2021-07-23 23:59 ` Alan Third
2021-07-24  0:34   ` Yuan Fu [this message]
2021-07-24  6:18     ` Eli Zaretskii

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=64C17491-439E-4538-9398-DA9DB0BB850E@gmail.com \
    --to=casouri@gmail.com \
    --cc=alan@idiocy.org \
    --cc=emacs-devel@gnu.org \
    /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).