Hi lldb-dev.
I want to be able to use LLDB inside of iPython, so I can have mixed python and
LLDB debug session.
To this end, I’d like to update LLDB to have full support for python file
objects, so the outputs of debugger commands can be redirected into iPython’s
own streams.
This howeve
Hi lldb-dev.
I can’t seem to figure out how to build a debug lldb on windows. It wants to
link against a debug version of Python, which isn’t there.
My cmake line looks like this:
cmake -G Ninja `
> On Sep 23, 2019, at 7:11 AM, Pavel Labath wrote:
>
> On 20/09/2019 17:35, Larry D'Anna via lldb-dev wrote:
>> Hi lldb-dev.
>> I want to be able to use LLDB inside of iPython, so I can have mixed python
>> and LLDB debug session.
>> To this end, I’d li
> On Sep 24, 2019, at 4:11 AM, Pavel Labath wrote:
>
> On 23/09/2019 20:54, Larry D'Anna wrote:
>>> On Sep 23, 2019, at 7:11 AM, Pavel Labath wrote:
>>>
>>> On 20/09/2019 17:35, Larry D'Anna via lldb-dev wrote:
>>>> Hi lldb-dev.
>
Pavel Labath said
> some llvm classes, are so well-known and widely used, that qualifying
> them with "llvm::" serves no useful purpose and only adds visual noise.
> I'm thinking here mainly of ADT classes like String/ArrayRef,
> Optional/Error, etc. I propose we stop explicitly qualifying thes
Hi lldb-dev.
Most of the tests build binaries to test with using Makefiles, and these
Makefiles use all sorts of unix commands
like sed and uname.And yet I see the build-bot is running `ninja-check
lldb` on windows.
I thought maybe if I installed MinGW that would have enough stuff in i
The comments in File.h say:
// NB this enum is used in the lldb platform gdb-remote packet
// vFile:open: and existing values cannot be modified.
enum OpenOptions {
eOpenOptionRead = (1u << 0), // Open file for reading
eOpenOptionWrite = (1u << 1), // Open file for writing
eOpen
