From: "Mattias Engdegård" <mattias.engdegard@gmail.com>
To: "Gerd Möllmann" <gerd.moellmann@gmail.com>
Cc: 66575@debbugs.gnu.org
Subject: bug#66575: [PATCH] Gud lldb support
Date: Mon, 16 Oct 2023 15:30:23 +0200 [thread overview]
Message-ID: <7A4E9221-C0A4-4A98-A80A-5FD58C95C014@gmail.com> (raw)
In-Reply-To: <m2il76wzeg.fsf@Mini.fritz.box>
> No MI support, because lldb-mi is no longer part of LLVM.
So what is the currently blessed way to communicate with LLDB?
I only have comments about trivialities here; someone else should deal with the serious stuff.
> +(eval-when-compile (require 'rx))
There is usually no need to import rx explicitly. The necessary macros and functions are autoloaded.
> +;; because gud-symbol uses their values if they are present. Tehir
> +;; names are deducded from the minor-mode name.
'Their', 'deduced'.
> + ;; frame #0: ...) at emacs.c:1310:9 [opt]
> + (string-match (rx (and line-start (0+ blank) "frame"
> + (0+ not-newline) " at "
> + (group (1+ (not (any ":"))))
> + ":"
(You can write (not ":") instead of (not (any ":")) if you like.)
If the file name can have an absolute directory part, then it may run into trouble on Windows (C:\Some\Dir\File.c).
Sad that we throw away the column number here, but perhaps that's just a limitation of gud.el.
Anyway, a big step up from not having any support at all. Thank you!
Would you include a NEWS entry as well?
next prev parent reply other threads:[~2023-10-16 13:30 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-16 12:00 bug#66575: [PATCH] Gud lldb support Gerd Möllmann
2023-10-16 13:30 ` Mattias Engdegård [this message]
2023-10-16 13:57 ` Mattias Engdegård
2023-10-16 14:46 ` Mattias Engdegård
2023-10-17 8:15 ` Gerd Möllmann
2023-10-16 14:09 ` Gerd Möllmann
2023-10-17 9:00 ` Mattias Engdegård
2023-10-17 10:03 ` Gerd Möllmann
2023-10-17 11:21 ` Mattias Engdegård
2023-10-17 12:30 ` Gerd Möllmann
2023-10-17 16:18 ` Mattias Engdegård
2023-10-17 16:55 ` Gerd Möllmann
2023-10-17 17:18 ` Gerd Möllmann
2023-10-17 15:40 ` Gerd Möllmann
2023-10-17 16:27 ` Mattias Engdegård
2023-10-17 17:01 ` 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=7A4E9221-C0A4-4A98-A80A-5FD58C95C014@gmail.com \
--to=mattias.engdegard@gmail.com \
--cc=66575@debbugs.gnu.org \
--cc=gerd.moellmann@gmail.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 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).