Thank you for the feedback. I'll look into how to get the expressions
cleared when the breakpoint locations get unresolved. I can also
switch the breakpoints to a weak_ptr if you think that is worthwhile,
but one of the two fixes is enough for me at the moment.
regards,
pavel
On 22 February 2017
I uploaded a CL for review what fixes the crash you are experimenting at
https://reviews.llvm.org/D30251 (we are mapping the files into memory as
read only and then trying to write into it) but I think nobody tests LLDB
with relocable object files so you might run into a lot of bugs in the way.
Als
> On Feb 21, 2017, at 5:08 PM, Jim Ingham wrote:
>
>>
>> On Feb 21, 2017, at 4:49 PM, Jim Ingham via lldb-dev
>> wrote:
>>
>>
>>> On Feb 21, 2017, at 4:24 PM, Greg Clayton via lldb-dev
>>> wrote:
>>>
- StepOverBreakpointTestCase: Have the test not store the breakpoints
in the t
According to the schedule on llvm.org, we should have tagged 'final'
yesterday, so the release is now officially a little behind schedule.
There are currently seven blockers (llvm.org/pr31622). Several of them
have patches. If you can help reviewing them, please do so.
- PR30256: Assert in llvm::
Hello. I am Lee.
I have trouble to run lldb.
My system is Ubutu 16.10-server & downloaded lldb version 3.8.1 via apt-get
install.
I wand just local debugging. But err message is like below.
tt@ttt:~/trunk$ lldb /system/bin/cwm
Traceback (most recent call last):
File "", line 1, in
Imp
Hello. I am Lee.
I have trouble to run lldb.
My system is Ubutu 16.10-server & downloaded lldb version 3.8.1 via apt-get
install.
I wand just local debugging. But err message is like below.
tt@ttt:~/trunk$ lldb /system/bin/cwm
Traceback (most recent call last):
File "", line 1, in
Imp
