This patch teaches lldb to detect when there are missing frames in a
backtrace due to a sequence of tail calls, and to fill in the backtrace
with artificial tail call frames when this happens. This is only done
when the execution history can be determined from the call graph and
from the return PC addresses of calls on the stack. Ambiguous sequences
of tail calls (e.g anything involving tail calls and recursion) are
detected and ignored.
Depends on D49887.
Does this also work for C functions? If yes, would symbol_name be a more accurate description?
Is this pointer globally unique in the program, or can two mangled names appear in a legal C program that don't refer to the same function?