diff options
| author | Jonas Devlieghere <jonas@devlieghere.com> | 2020-05-05 15:59:43 -0700 |
|---|---|---|
| committer | Jonas Devlieghere <jonas@devlieghere.com> | 2020-05-05 16:05:49 -0700 |
| commit | 0274c797c65a720010aee7f40cff621cd993ba15 (patch) | |
| tree | 16633d6288badff274dadb38d231918e9f36a452 /clang/lib/Frontend/CompilerInvocation.cpp | |
| parent | b0eb7cd2be849f0551e9b05a0cbf2d59d8c9f50d (diff) | |
| download | llvm-0274c797c65a720010aee7f40cff621cd993ba15.zip llvm-0274c797c65a720010aee7f40cff621cd993ba15.tar.gz llvm-0274c797c65a720010aee7f40cff621cd993ba15.tar.bz2 | |
[lldb/Utils] Serialize exit code in lldb-repro.py
After 61d5b0e66394 more shell test are expected to exit with a non-zero
status code. Because the exit status is computed in the driver and not
behind the SB API layer, reproducers don't know about it and always
return 0 unless replay failed.
This discrepancy means that these tests don't work with lldb-repro.py
and skipping them for this reason would be a pity. To solve this
problem, the script now serializes the exit code during capture and
returns that during replay.
These is an assert that ensures that replay exits with a zero exit
status to prevent replay failures from being silently ignored.
Diffstat (limited to 'clang/lib/Frontend/CompilerInvocation.cpp')
0 files changed, 0 insertions, 0 deletions
