search for: d54187

...of extra information involved would help us design around it. Note that the current Dexter codebase is going to be significantly remangled, we're trying to decouple the expected-behaviour language from the debugger-abstractions summary of how the program behaved. [0] https://reviews.llvm.org/D54187#1290282 [1] https://github.com/SNSystems/dexter [2] https://www.youtube.com/watch?v=XRT_GmpGjXE [3] https://llvm.org/devmtg/2018-04/slides/Bedwell-Measuring_the_User_Debugging_Experience.pdf [4] https://github.com/jmorse/dexter/tree/f46f13f778484ed5c6f7bf33b8fc2d4837ff7265/tests/nostdlib/llvm_passe...

...ting anything less than a perfect score is considered a failure. The test commands are debugger-agnostic, allowing the same test to be run with any supported debugger. The compiler and debugger to use in the test are specified on the command line. In a previous discussion [https://reviews.llvm.org/D54187], the idea of using Dexter to drive the debuginfo-tests was raised as a solution to adding cdb support without needing to maintain an entirely separate suite of tests (as is currently the case). It can also replace the existing llgdb layer, which provides a frontend for driving tests with GDB and L...