On 8/22/19 12:36 AM, Ismail Bennani via lldb-dev wrote:
>> On Aug 21, 2019, at 3:48 PM, Pedro Alves wrote:
>> Say, you're using a 5 bytes jmp instruction to jump to the
>> trampoline, so you need to replace 5 bytes at the breakpoint address.
>> But the instruction at the breakpoint address is sho
Hey Jim,
We just noticed that 'target.experimental.inject-local-vars' is true by
default. If we disable that experimental the performance for expression
evaluation is significantly better.
>From the flag description:
"If true, inject local variables explicitly into the expression text. This
will
https://bugs.llvm.org/show_bug.cgi?id=43091
Bug ID: 43091
Summary: lldb very slow single stepping rep stosb
Product: lldb
Version: unspecified
Hardware: PC
OS: Linux
Status: NEW
Severity: enhancement
The test
lldb/packages/Python/lldbsuite/test/lang/cpp/member-and-local-vars-with-same-name/main.cpp
is testing this feature, so you should get a 10 (instead of a correct
12345) when you break in main.cpp:31 in this test and eval "expr a"
while you have this feature disabled. At least for me that's
Another possibility is to have the IDE insert NOP opcodes for you when you
write a breakpoint with a condition and compile NOPs into your program.
So the flow is:
- set a breakpoint in IDE
- modify breakpoint to add a condition
- compile and debug, the IDE inserts NOP instructions at the right p
Hi Greg,
Thanks for your suggestion!
> On Aug 22, 2019, at 3:35 PM, Greg Clayton wrote:
>
> Another possibility is to have the IDE insert NOP opcodes for you when you
> write a breakpoint with a condition and compile NOPs into your program.
>
> So the flow is:
> - set a breakpoint in IDE
> -
> On Aug 22, 2019, at 3:58 PM, Ismail Bennani via lldb-dev
> wrote:
>
> Hi Greg,
>
> Thanks for your suggestion!
>
>> On Aug 22, 2019, at 3:35 PM, Greg Clayton wrote:
>>
>> Another possibility is to have the IDE insert NOP opcodes for you when you
>> write a breakpoint with a condition an
If you can rely on the IDE & compile&debug, you might as well made the
IDE&compiler
bake in the breakpoint condition and trompoline into the code without having to
have
the debugger build the trampoline afterwards.
Thanks,
Pedro Alves
On 8/22/19 11:35 PM, Greg Clayton wrote:
> Another possibili
On 23/08/2019 00:58, Ismail Bennani via lldb-dev wrote:
Hi Greg,
Thanks for your suggestion!
On Aug 22, 2019, at 3:35 PM, Greg Clayton wrote:
Another possibility is to have the IDE insert NOP opcodes for you when you
write a breakpoint with a condition and compile NOPs into your program.
S
