When I am using `bt` to look at my backtrace, I get for a method call
breakpoint in `+[Hello printName:version:]` a stacktrace like this (with
my custom Objective-C runtime):
```
* frame #0: 0x004179b3 test-debugger`+[Hello
printName:version:](self=Hello, _cmd=,
_param=0x7ff
On 22/09/2019 20:20, Larry D'Anna via lldb-dev wrote:
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 `
"-DPYTHON_HOME=C:\Program File
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 like to update LLDB to have full support for python
file objects, so the outputs of debugger commands can b
Hi Larry,
You can tell the Python installer to install the debug libraries.
I recently switch from VS 2015 to VS 2017 to build LLDB. My debug builds
stopped working – it couldn’t link with the Python debug library, even though I
had it in the right place. My guess is the Python I’m using (3.5.1
I think the best mechanism for this would be to ensure that the trampolines are
marked up as DW_AT_artificial and/or DW_AT_trampoline by the compiler. I'm
pretty sure LLDB then already knows how to hide artificial frames (somebody
else can probably provide pointers for how that works).
-- adria
On 19 Sep 2019, at 16:51, Hans Wennborg via Release-testers
wrote:
>
> On Tue, Sep 17, 2019 at 4:05 PM Hans Wennborg wrote:
>>
>> 9.0.0-rc6 was just tagged from the release_90 branch at r372100. In
>> the Git monorepo, it's tagged as llvmorg-9.0.0-rc6.
>
> This has now been tagged as the fina
At some point it would be good to add trampoline support at the Python level.
You can produce scripted thread plans now - and the trampoline mechanism just
returns a thread plan to step through the trampoline... It would be neat to be
able to support other systems without having to build them
> 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 like to update LLDB to have full support fo
> On Sep 21, 2019, at 11:11 AM, Nikita Karetnikov wrote:
>
> Jim,
>
> > My model for this sort of tracing activity is that you are writing a fancy
> > kind
> > of “step” operation. You would write a fancy step & record plan that would
> > proceed along however you wanted and log at each stop
On 23.09.19 19:22, Adrian Prantl wrote:
I think the best mechanism for this would be to ensure that the trampolines are
marked up as DW_AT_artificial and/or DW_AT_trampoline by the compiler. I'm
pretty sure LLDB then already knows how to hide artificial frames (somebody
else can probably pro
https://bugs.llvm.org/show_bug.cgi?id=43421
Bug ID: 43421
Summary: Prologue computation is incorrect for single-line
functions compiled by GCC
Product: lldb
Version: 6.0
Hardware: PC
OS: Linux
St
Jim,
>> Not sure if my current version of 'SimpleStep' is correct (I've made a
few
>> changes since testing via 'thread step-scripted'), but nothing happens
(no
>> prints on '__init__') when I add the class via
'StepUsingScriptedThreadPlan' in
>> the callback.
>>
>> What's the proper way to do thi
12 matches
Mail list logo
