From: "Gerd Möllmann" <gerd.moellmann@gmail.com>
To: "Mattias Engdegård" <mattias.engdegard@gmail.com>
Cc: 66604@debbugs.gnu.org
Subject: bug#66604: [PATCH] Gud LLDB completions
Date: Thu, 19 Oct 2023 15:08:55 +0200 [thread overview]
Message-ID: <m2ttqmep3s.fsf@Pro.fritz.box> (raw)
In-Reply-To: <D7541157-4811-4176-97BA-49B5083D0F6B@gmail.com> ("Mattias Engdegård"'s message of "Thu, 19 Oct 2023 14:29:26 +0200")
Mattias Engdegård <mattias.engdegard@gmail.com> writes:
> 19 okt. 2023 kl. 13.50 skrev Gerd Möllmann <gerd.moellmann@gmail.com>:
>>> script --language python -- print('Gud initialized')
>>>
>>> is apparently sent twice. Perhaps something simpler can be sent, and
>>> only once?
>>
>> Hm, I'm sending it once
>
> Sorry, you are perfectly right. The code is
>
> (gud-basic-call "script --language python -- print('Gud initialized')")
> (gud-basic-call "script --language python -- print('Gud initialized.')"))
>
> so you are actually sending two slightly different commands.
Fixed, apparently I can't smerge.
>>> 2. Sometimes there's an extra (second) space after the (lldb) prompt,
>>> typically after stopping. No idea where that comes from.
>>
>> Hm, I don't think I see that here. Is it immediately after the stop, or
>> does it come later?
>
> Just after the stop. Transcript (with line numbers for reference):
>
> 01|(lldb) b exec_byte_code
> 02|Breakpoint 2: where = emacs`exec_byte_code + 20 at bytecode.c:476:33, address = 0x000000010b389b84
> 03|(lldb) c
> 04|Process 13507 resuming
> 05|(lldb) emacs was compiled with optimization - stepping may behave oddly; variables may not be available.
> 06|(lldb) Process 13507 stopped
> 07|* thread #1, queue = 'com.apple.main-thread', stop reason = breakpoint 2.1
> 08| gud-info: (gud-lldb-stop :file ////Users/mattias/emacs/src/bytecode.c/// :line 476 :column 33)
> 09|Target 0: (emacs) stopped.
> 10|(lldb) <cursor here>
>
> In lines 5 and 6, an (lldb) prompt is printed although no input takes
> place there. No such prompts are seen when lldb runs in a terminal.
> Line 6 also prefixes "Process" with an extra space which isn't present
> when running in a terminal either.
I don't really know, but the only thing interacting with the lldb
process in addition to what is done "normally" is completion. Could you
please set completion-at-point-functions to nil in the lldb buffer, and
see if that's also happening then?
>
>> It's a bit overkill ATM, but you must admit that it's elegant :-).
>
> Overkill is the least of it. Just you wait until someone makes you debug some crafted source code that causes your Emacs to evaluate arbitrary Lisp expressions!
>
> In general:
> 1. Don't use `eval` for parsing data.
> 2. Don't use `eval`.
3. Don't use CL.
I'll have a look tomorrow.
next prev parent reply other threads:[~2023-10-19 13:08 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-18 11:25 bug#66604: [PATCH] Gud LLDB completions Gerd Möllmann
2023-10-18 13:37 ` Mattias Engdegård
2023-10-18 14:42 ` Gerd Möllmann
2023-10-18 15:14 ` Mattias Engdegård
2023-10-18 15:23 ` Gerd Möllmann
2023-10-18 16:05 ` Mattias Engdegård
2023-10-18 16:57 ` Gerd Möllmann
2023-10-18 18:55 ` Gerd Möllmann
2023-10-19 10:34 ` Mattias Engdegård
2023-10-19 10:48 ` Gerd Möllmann
2023-10-19 11:36 ` Mattias Engdegård
2023-10-19 11:50 ` Gerd Möllmann
2023-10-19 12:29 ` Mattias Engdegård
2023-10-19 13:08 ` Gerd Möllmann [this message]
2023-10-19 13:22 ` Mattias Engdegård
2023-10-20 6:04 ` Gerd Möllmann
2023-10-20 10:42 ` Mattias Engdegård
2023-10-20 11:12 ` Gerd Möllmann
2023-10-20 11:50 ` Mattias Engdegård
2023-10-20 11:59 ` Gerd Möllmann
2023-10-20 17:28 ` Gerd Möllmann
2023-10-20 17:47 ` Gerd Möllmann
2023-10-21 10:32 ` Gerd Möllmann
2023-10-21 10:51 ` Mattias Engdegård
2023-10-21 12:33 ` Gerd Möllmann
2023-10-21 10:37 ` Mattias Engdegård
2023-10-21 10:50 ` Gerd Möllmann
2023-10-23 5:31 ` Gerd Möllmann
2023-10-23 17:18 ` Mattias Engdegård
2023-10-23 17:57 ` Gerd Möllmann
2023-10-23 20:51 ` Mattias Engdegård
2023-10-24 4:35 ` Gerd Möllmann
2023-10-24 8:47 ` Mattias Engdegård
2023-10-24 8:52 ` Gerd Möllmann
2023-10-24 10:00 ` Mattias Engdegård
2023-10-24 10:27 ` Gerd Möllmann
2023-10-24 18:12 ` Mattias Engdegård
2023-10-25 4:29 ` Gerd Möllmann
2023-10-18 15:24 ` Gerd Möllmann
2023-10-19 6:31 ` Visuwesh
2023-10-19 6:56 ` 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=m2ttqmep3s.fsf@Pro.fritz.box \
--to=gerd.moellmann@gmail.com \
--cc=66604@debbugs.gnu.org \
--cc=mattias.engdegard@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).