This patch adds a "DexCommandLine" command, allowing dexter tests to specify what command line options the test should be started with. I've also plumbed it through into the debuggers.
Details
Details
Diff Detail
Diff Detail
- Repository
- rG LLVM Github Monorepo
Event Timeline
Comment Actions
Looks good, LGTM with two questions inline.
| cross-project-tests/debuginfo-tests/dexter/dex/debugger/DebuggerControllers/DebuggerControllerBase.py | ||
|---|---|---|
| 33 | Probably a better user experience if this is caught in the parsing stage and prettily reported as an error. wdyt? | |
| cross-project-tests/debuginfo-tests/dexter/feature_tests/commands/perfect/command_line.c | ||
| 10–13 | Is this part of the test (and the #include) necessary? | |
Comment Actions
Produce a parsing error if DexCommandLine is specified more than once; refresh a test.
| cross-project-tests/debuginfo-tests/dexter/dex/debugger/DebuggerControllers/DebuggerControllerBase.py | ||
|---|---|---|
| 33 | I've added a filter to ParseCommand.py, which I think is the correct place for validating these things? | |
| cross-project-tests/debuginfo-tests/dexter/feature_tests/commands/perfect/command_line.c | ||
| 10–13 | Yup, that was due to some testing, now removed. | |
Comment Actions
(Still LGTM)
| cross-project-tests/debuginfo-tests/dexter/dex/debugger/DebuggerControllers/DebuggerControllerBase.py | ||
|---|---|---|
| 33 | Thanks, and yeah that's the right place. | |
Probably a better user experience if this is caught in the parsing stage and prettily reported as an error. wdyt?