Hello, I'm new to hacking on the compiler. I've got to the stage where I'm running
x.py test src/test/ui/whateverand trying to figure out why my change to the parser isn't working properly.
I thought it might be helpful to step through the parser while it's building one of the test source files. What's the best way to run an
x.py test under a debugger?
I usually do something like
gdb --args ./build/x86_64-pc-windows-gnu/stage1/bin/rustc src/test/ui/name.rs, but that becomes more annoying when there are dependencies in
auxiliary, so integrating that into
x.py test would be really great.
btw, I wonder if this is explained on rustc-guide, because otherwise seems like an interesting thing to explain
As far as I could see, the rustc-guide only mentions using backtraces or debug logging.