diff options
| author | David Spickett <david.spickett@linaro.org> | 2021-09-23 13:28:24 +0000 |
|---|---|---|
| committer | David Spickett <david.spickett@linaro.org> | 2021-09-24 08:32:11 +0000 |
| commit | 0a36c72dee61a0a97805a3cd297572ad0c38d979 (patch) | |
| tree | 63c87cad2365cd2605c82090b4d00572003bc654 /llvm/lib/Analysis/ValueTracking.cpp | |
| parent | ea92283449f9b132531ef152625e3e799395e449 (diff) | |
| download | llvm-0a36c72dee61a0a97805a3cd297572ad0c38d979.zip llvm-0a36c72dee61a0a97805a3cd297572ad0c38d979.tar.gz llvm-0a36c72dee61a0a97805a3cd297572ad0c38d979.tar.bz2 | |
[libcxx][pretty printers] Check GDB Python scripting support
I found this after upgrading from Ubuntu bionic (gdb 8.1.1) to
Focal (gdb 9.2). (where this test fails, but that's for a
different patch)
9.2 allows you to set breakpoint commands from
Python, which was added in 8.3.
(bintutils a913fffbdee21fdd50e8de0596358be425775678
"Allow breakpoint commands to be set from Python")
The reason this test never failed before was because it did so
silently. "source <python file>" doesn't fail even if that script
raises an Exception.
To fix this extend the gdb lit feature to check that:
* gdb exists
* has Python support
* allows you to set breakpoint commands
Reviewed By: #libc, ldionne
Differential Revision: https://reviews.llvm.org/D110334
Diffstat (limited to 'llvm/lib/Analysis/ValueTracking.cpp')
0 files changed, 0 insertions, 0 deletions