llvm-project/lldb/test/API/functionalities/tail_call_frames
Vedant Kumar 03e29e2c19 [lldb/DWARF] Reland: Use DW_AT_call_pc to determine artificial frame address
Reland with changes: the test modified in this change originally failed
on a Debian/x86_64 builder, and I suspect the cause was that lldb looked
up the line location for an artificial frame by subtracting 1 from the
frame's address. For artificial frames, the subtraction must not happen
because the address is already exact.

---

lldb currently guesses the address to use when creating an artificial
frame (i.e., a frame constructed by determining the sequence of (tail)
calls which must have happened).

Guessing the address creates problems -- use the actual address provided
by the DW_AT_call_pc attribute instead.

Depends on D76336.

rdar://60307600

Differential Revision: https://reviews.llvm.org/D76337
2020-03-24 12:54:40 -07:00
..
ambiguous_tail_call_seq1
ambiguous_tail_call_seq2
cross_dso
cross_object
disambiguate_call_site
disambiguate_paths_to_common_sink
disambiguate_tail_call_seq
inlining_and_tail_calls
sbapi_support
thread_step_out_message
thread_step_out_or_return
unambiguous_sequence [lldb/DWARF] Reland: Use DW_AT_call_pc to determine artificial frame address 2020-03-24 12:54:40 -07:00