diff options
| author | jimingham <jingham@apple.com> | 2024-10-30 09:28:38 -0700 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2024-10-30 09:28:38 -0700 |
| commit | 7dbbd2b251412b7b0809aabe672f3f57f0805dbb (patch) | |
| tree | 7f39de61fb9eae824798dc5dea7ff2ef011828ff /lldb/source/Plugins/ScriptInterpreter/Python/SWIGPythonBridge.h | |
| parent | 9cd30b1ef311edb0aa0527bead52e2fc490160ef (diff) | |
| download | llvm-7dbbd2b251412b7b0809aabe672f3f57f0805dbb.zip llvm-7dbbd2b251412b7b0809aabe672f3f57f0805dbb.tar.gz llvm-7dbbd2b251412b7b0809aabe672f3f57f0805dbb.tar.bz2 | |
Fix call site breakpoint patch (#114158)
This fixes the two test suite failures that I missed in the PR:
https://github.com/llvm/llvm-project/pull/112939
One was a poorly written test case - it assumed that on connect to a
gdb-remote with a running process, lldb MUST have fetched all the frame
0 registers. In fact, there's no need for it to do so (as the CallSite
patch showed...) and if we don't need to we shouldn't. So I fixed the
test to only expect a `g` packet AFTER calling read_registers.
The other was a place where some code had used 0 when it meant
LLDB_INVALID_LINE_NUMBER, which I had fixed but missed one place where
it was still compared to 0.
Diffstat (limited to 'lldb/source/Plugins/ScriptInterpreter/Python/SWIGPythonBridge.h')
0 files changed, 0 insertions, 0 deletions