> From: Ilia K
> Date: Thu, 17 Aug 2017 14:59:01 +0300
> Cc: LLDB
>
> Did you build it from sources? If yes, please provide your configure options.
No, I installed the snapshot available from https://llvm.org/builds/.
(I used the 32-bit binaries from there.)
Since at least two snapshots ago, lldb-mi no longer works on
MS-Windows:
D:\usr\archive>lldb-mi d:\usr\bin\emacs.exe
MI: Error: Driver. LLDB Debugger.
MI: Error: Driver Manager. Driver 'Machine Interface Driver Version: 1.0.0.9'
(ID:'MIDriver') initialise failed. Driver. LLDB Debugger.
It
> From: Ilia K
> Date: Sun, 6 Aug 2017 13:20:13 +0300
> Cc: Ted Woodward , yllumin...@gmail.com,
> jan.kratoch...@redhat.com, LLDB
>
> You are probably got it but yes, -file-list-exec-source-files and -break-list
> commands are not implemented yet.
> I'll try to find the time to fix it.
> From: "Ted Woodward"
> Cc:
> Date: Mon, 31 Jul 2017 13:24:31 -0500
>
> The best thing to do is give us a list of commands that are failing, in a bug
> opened in Bugzilla at http://bugs.llvm.org .
The URL I provided (after several mistaken attempts ;-) included a
lits of the failing commands.
On July 30, 2017 7:15:29 AM GMT+03:00, Eli Zaretskii via lldb-dev
wrote:
> On July 30, 2017 7:05:52 AM GMT+03:00, Eli Zaretskii via lldb-dev
> wrote:
> > On July 30, 2017 6:30:04 AM GMT+03:00, Zachary Turner
> > wrote:
> > > Are we talking about some kind of m
On July 30, 2017 7:05:52 AM GMT+03:00, Eli Zaretskii via lldb-dev
wrote:
> On July 30, 2017 6:30:04 AM GMT+03:00, Zachary Turner
> wrote:
> > Are we talking about some kind of mi support other than lldb's
> > existing MI
> > interface? Afaik it works reasonably
f you can figure out where the deficiencies are in the existing mi
> implementation, patches are always welcome
> On Sat, Jul 29, 2017 at 7:39 PM Eli Zaretskii via lldb-dev <
> lldb-dev@lists.llvm.org> wrote:
>
> > > Date: Sat, 29 Jul 2017 22:43:59 +0200
> > > Cc:
> Date: Sat, 29 Jul 2017 22:43:59 +0200
> Cc: lldb-dev@lists.llvm.org
> From: Jan Kratochvil via lldb-dev
>
> MI protocol was designed to minimize the amount of data transferred between
> gdb/lldb and a front end. But this communication isn't anything expensive as
> the debugger always runs on t
> From: Russell Greene
> Date: Tue, 04 Apr 2017 14:50:23 +
> Cc: ted.woodw...@codeaurora.org, lldb-dev@lists.llvm.org
>
> Well I would guess the main problem is lldb being compiled in a msys
> environment which I guess lldb
> recognizes to be so posix to try and launch lldb-server. The resul
> Date: Tue, 04 Apr 2017 03:00:21 +
> From: Zachary Turner via lldb-dev
>
> As the person who added most of the support for debugging Windows
> executables, I can tell you that I never
> tested a MinGW executable (nor was it one of my original goals). It doesn't
> entirely surprise me that
> From: Zachary Turner
> Date: Tue, 06 Dec 2016 16:22:51 +
>
> I have never seen either of those problems, but I can test it out and see if
> I can reproduce.
Thanks.
If you are unable to reproduce, I wonder why it happens to me. The
system where I installed lldb is just a vanilla Windows
> Date: Tue, 15 Nov 2016 18:08:03 +0200
> Cc: lldb-dev@lists.llvm.org
> From: Eli Zaretskii via lldb-dev
>
> > From: Rudy Pons
> > Date: Tue, 15 Nov 2016 01:08:52 +0100
> > Cc: lldb-dev@lists.llvm.org
> >
> > I had a similar crash, and submitted a pa
> From: Rudy Pons
> Date: Tue, 15 Nov 2016 01:08:52 +0100
> Cc: lldb-dev@lists.llvm.org
>
> I had a similar crash, and submitted a patch commited in rL285843
> You could try to build afte this version from source, or wait for an updated
> build.
Thanks, I will have to wait, as I don't have MSVC
Hi,
I installed a 32-bit Windows build of LLVM 4.0.0 from this page:
http://llvm.org/builds/
where it is identified as "based on SVN r284979 (24 October 2016)".
(I actually wanted only LLDB, but there doesn't seem to be a separate
installer for that.) The machine where I installed it runs the
14 matches
Mail list logo
