https://llvm.org/bugs/show_bug.cgi?id=26139
Bug ID: 26139
Summary: CommandScriptImmediateOutputTestCase fails on Linux
Product: lldb
Version: unspecified
Hardware: PC
OS: Linux
Status: NEW
Severity: normal
>
> VS 2013 support is going to be deprecated soon. At that point it could
break any time, because nobody is going to be making an effort to keep it >
> working.
>
How is this going to play with Python scripting on Windows? Given
that LLDB only supports Python 2.7 bindings,
and that Python 2.7
When we move to VS 2015 (which will be soon, btw) we will require Python
3.5+ on Windows. This already works for the most part, you can even try it
out today. I've spent the better part of the past 6 months making LLDB's
python bindings work with Python 3. The best part is that you don't need
to
Hi again, everyone
I’d like to ping on this patch now that the 3.8 branch is fairly new, and
merging it over is fairly straight-forward.
Thanks in advance for your comments!
- Will
> There is a small change that enables correct calculation of arm sub
> architectures while using the REPL on a
So this is biting us again, for unrelated reasons. I thought of a
potentially interesting solution. Right now each test class has a setUp
and tearDown method. This method is called before and after EVERY test
method in the class. So you can't put anything in these methods unless
it's common to
Hi,
We are building an IDE debugger on top of lldb python API. In order to get
the source remapping work(the source path embedded in the symbol may be
different from the real source path), user needs to use "settings set
target.source-map" command to remap the source.
I would like users to do sim
There is currently no API to access the settings. You have to cons up commands
and use SBCommandInterpreter::HandleCommand to execute them.
This is one of the remaining holes in the SB API.
Jim
> On Jan 14, 2016, at 2:41 PM, Jeffrey Tan via lldb-dev
> wrote:
>
> Hi,
>
> We are building an
