projects / platform / upstream / llvm.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: d52ed84) | patch
The compiler may use "line number 0" to indicate compiler generated goo that it can't
authorJim Ingham <jingham@apple.com>
Wed, 3 Feb 2016 00:07:23 +0000 (00:07 +0000)
committerJim Ingham <jingham@apple.com>
Wed, 3 Feb 2016 00:07:23 +0000 (00:07 +0000)
commit39f7353a60e930a304880508e2af116c6f90ec7d
tree3ced46488ecc0a3508b6d3248ab3517cb23ea46btree | snapshot
parentd52ed84160f3c07a04bdc48eef81ba6a0ffc3f8ccommit | diff
The compiler may use "line number 0" to indicate compiler generated goo that it can't
track a source for.  When we are pushing breakpoints and stepping past function prologues,
also push past code from line 0 immediately following the prologue end.

<rdar://problem/23730696>

llvm-svn: 259611
lldb/include/lldb/Symbol/Function.h diff | blob | history
lldb/source/Symbol/Function.cpp diff | blob | history
Domain: System / Toolchain;