Thanks for the help with this.
The problem is that lldb would try to advance the return breakpoint in
no_debug_caller:
(lldb) disass -b
a.out`no_debug_caller:
0x4005dd <+0>: 55pushq %rbp
0x4005de <+1>: 48 89 e5 movq %rsp, %rbp
0x4005e1 <+4>: 4
Thanks Siva, I'll revert the change. I have access to a linux machine but I
haven't used it in a long time. Would it be easy to send me the binary (with
debug info) for this test case so I can see what gcc emitted here and figure
out how it went wrong? This test passes with clang on x86_64 da
This broke TestStepNoDebug, atleast on Linux when inferior is compiled
with GCC:
http://lab.llvm.org:8011/builders/lldb-x86_64-ubuntu-14.04-cmake/builds/10091
I am able to reproduce this on my machine. Let me know if you need any
help with anything.
On Thu, Jan 7, 2016 at 4:06 PM, Jason Molenda
Author: jmolenda
Date: Thu Jan 7 18:06:03 2016
New Revision: 257117
URL: http://llvm.org/viewvc/llvm-project?rev=257117&view=rev
Log:
Performance improvement: Change lldb so that it puts a breakpoint
on the first branch instruction after a function return (or the end
of a source line), instead of
