786bab4334
It isn't useful for users to see "<unknown>" as a stack trace when lldb fails to symbolicate a stack frame. I've replaced "<unknown>" with the value of the program counter instead. Test Plan: To test this, I opened a target that lldb fails to symbolicate in VSCode, and observed in the CALL STACK section that instead of being shown as "<unknown>", those stack frames are represented by their program counters. I added a new test case, `TestVSCode_stackTraceMissingFunctionName` that exercises this feature. I also ran `lldb-dotest -p TestVSCode` and saw that the tests passed. Differential Revision: https://reviews.llvm.org/D156732
7 lines
141 B
C++
7 lines
141 B
C++
int main() {
|
|
typedef void (*FooCallback)();
|
|
FooCallback foo_callback = (FooCallback)0;
|
|
foo_callback(); // Crash at zero!
|
|
return 0;
|
|
}
|