diff options
| author | Vedant Kumar <vsk@apple.com> | 2019-11-01 17:20:38 -0700 |
|---|---|---|
| committer | Vedant Kumar <vsk@apple.com> | 2019-11-04 15:14:24 -0800 |
| commit | a5c8ec4baa2c00d8dbca36ffd236a40f9e0c07ed (patch) | |
| tree | bbc1abab174808a5f28554669bd911c8ced6c246 /lldb/source/Plugins/ScriptInterpreter/Python/ScriptInterpreterPythonImpl.h | |
| parent | dc34b1c94df683eb85df989c1d62c81c588a29f8 (diff) | |
| download | llvm-a5c8ec4baa2c00d8dbca36ffd236a40f9e0c07ed.zip llvm-a5c8ec4baa2c00d8dbca36ffd236a40f9e0c07ed.tar.gz llvm-a5c8ec4baa2c00d8dbca36ffd236a40f9e0c07ed.tar.bz2 | |
[CGDebugInfo] Emit subprograms for decls when AT_tail_call is understood
Currently, clang emits subprograms for declared functions when the
target debugger or DWARF standard is known to support entry values
(DW_OP_entry_value & the GNU equivalent).
Treat DW_AT_tail_call the same way to allow debuggers to follow cross-TU
tail calls.
Pre-patch debug session with a cross-TU tail call:
```
* frame #0: 0x0000000100000fa4 main`target at b.c:4:3 [opt]
frame #1: 0x0000000100000f99 main`main at a.c:8:10 [opt]
```
Post-patch (note that the tail-calling frame, "helper", is visible):
```
* frame #0: 0x0000000100000fa4 main`target at b.c:4:3 [opt]
frame #1: 0x0000000100000f80 main`helper [opt] [artificial]
frame #2: 0x0000000100000f99 main`main at a.c:8:10 [opt]
```
rdar://46577651
Differential Revision: https://reviews.llvm.org/D69743
Diffstat (limited to 'lldb/source/Plugins/ScriptInterpreter/Python/ScriptInterpreterPythonImpl.h')
0 files changed, 0 insertions, 0 deletions