Closed russelltg closed 10 months ago
OS: Ubuntu 20.04 in docker VSCode version: 1.79.2 CodeLLDB version: 1.9.2 Compiler: Clang 16.0.6 Debuggee: x86_64-linux-gnu
I have this binary that when I debug, it crashes and LLDB catches that. But I can't see the stacktrace in the vscode window, just from the debug console with bt. In the vscode window, it shows "Can't read instructions at that address":
bt
Verbose log
I'm happy to provide more info if useful. I can email binaries as well, but would prefer to keep those private.
Edit: this seems to happy whenever the instruction pointer is invalid. This program repro's it:
int main() { using call_t = void(*)(); call_t call = nullptr; call(); }
int main() { using call_t = void(*)();
call_t call = nullptr; call();
}
OS: Ubuntu 20.04 in docker VSCode version: 1.79.2 CodeLLDB version: 1.9.2 Compiler: Clang 16.0.6 Debuggee: x86_64-linux-gnu
I have this binary that when I debug, it crashes and LLDB catches that. But I can't see the stacktrace in the vscode window, just from the debug console with
bt
. In the vscode window, it shows "Can't read instructions at that address":Verbose log
I'm happy to provide more info if useful. I can email binaries as well, but would prefer to keep those private.
Edit: this seems to happy whenever the instruction pointer is invalid. This program repro's it: