diff options
| author | Joel E. Denny <jdenny.ornl@gmail.com> | 2023-10-03 10:00:21 -0400 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2023-10-03 10:00:21 -0400 |
| commit | 3dc7039f244f5da7368b8ba2f0e419c7d851c851 (patch) | |
| tree | a826b3805195a996f0f7e517595253ec46ff1fed /lldb/packages/Python/lldbsuite/test/gdbclientutils.py | |
| parent | 9084934aa95ce01dd2ab18f5b6eedbdf4fdddeae (diff) | |
| download | llvm-3dc7039f244f5da7368b8ba2f0e419c7d851c851.zip llvm-3dc7039f244f5da7368b8ba2f0e419c7d851c851.tar.gz llvm-3dc7039f244f5da7368b8ba2f0e419c7d851c851.tar.bz2 | |
[lit] Fix shell commands with newlines (#67898)
In PR #65242 (landed as 9e739fdb85ac672f3e25e971d96e71823e07ebda), I
claimed that RUN lines cannot contain newlines. Actually, they can after
substitution expansion. More generally, a lit config file can define
substitutions or preamble commands containing newlines. While both of
those cases seem unlikely in practice,
[D154987](https://reviews.llvm.org/D154987) proposes PYTHON directives
where it seems very likely.
Regardless of the use case, without this patch, such newlines break
expansion of `%dbg(RUN: at line N)`, and the fix is simple.
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test/gdbclientutils.py')
0 files changed, 0 insertions, 0 deletions