aboutsummaryrefslogtreecommitdiff
path: root/lldb/source/Plugins/ScriptInterpreter/Python/ScriptedProcessPythonInterface.h
diff options
context:
space:
mode:
authorcmtice <cmtice@google.com>2023-10-22 15:42:55 -0700
committerGitHub <noreply@github.com>2023-10-22 15:42:55 -0700
commitefb0e9c0bda62ba4b1c5421baeb140016ff53c84 (patch)
tree261eb95409610acb5f89a96574fd3efb968afce2 /lldb/source/Plugins/ScriptInterpreter/Python/ScriptedProcessPythonInterface.h
parent9c5a5a421d40399b4aee5d26fb0266f8261333ce (diff)
downloadllvm-efb0e9c0bda62ba4b1c5421baeb140016ff53c84.zip
llvm-efb0e9c0bda62ba4b1c5421baeb140016ff53c84.tar.gz
llvm-efb0e9c0bda62ba4b1c5421baeb140016ff53c84.tar.bz2
[LLDB] Update breakpoint-command.test to use string instead of number. (#69796)
lldb/test/Shell/Breakpoint/breakpoint-command.test adds a python command, to be executed when a breakpoint hits, that writes out a number. It then runs, hits the breakpoint and checks that the number is present exactly once. The problem is that on some systems the test can be run in a filepath that happens to contain the number (e.g. auto-generated directory names). The number is then detected multiple times and the test fails. This patch fixes the issue by using a string instead, particularly a string with spaces, which is very unlikely to be auto-generated by any system.
Diffstat (limited to 'lldb/source/Plugins/ScriptInterpreter/Python/ScriptedProcessPythonInterface.h')
0 files changed, 0 insertions, 0 deletions