GNU bug report logs - #66604
[PATCH] Gud LLDB completions

Previous Next

Full log

Message #127 received at 66604 <at> debbugs.gnu.org (full text, mbox):

From: Gerd Möllmann <gerd.moellmann <at> gmail.com>
To: Mattias Engdegård <mattias.engdegard <at> gmail.com>
Cc: 66604 <at> debbugs.gnu.org
Subject: Re: bug#66604: [PATCH] Gud LLDB completions
Date: Wed, 25 Oct 2023 06:29:06 +0200

Mattias Engdegård <mattias.engdegard <at> gmail.com> writes:

> 24 okt. 2023 kl. 12.27 skrev Gerd Möllmann <gerd.moellmann <at> gmail.com>:
>
>> Hm, maybe we could write all the stuff to a temporary file, and then
>> "command source <that file>"
>
> Yes, but would make it more difficult to run lldb remote, wouldn't it?

I don't think so.

There are two cases, depending on what running lldb remote means:

1. Remote debugging in the lldb sense. Here, lldb runs locally and
connects to an llb-server running somwhere else. I don't think that's a
problem.

2. We run lldb on a remote machine using Tramp. For example

  C-x C-f /ssh:remote:some-file RET
  M-x lldb

In this case, we have to oake sure that we write the commands file
on the right machine, but I think that should already work, modulo bugs.

BTW, I filed bug#66738 now, after building from a fresh master. Could
you please also have a look?

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.