2 ms·
Don't worry. No hard feelings. I agree that if there is a debugger available it's much better to use the debugger. [1] When I'm improving the optimization pas
by gus_massa 6y ago
Don't worry. No hard feelings.
I agree that if there is a debugger available it's much better to use the debugger. [1]
When I'm improving the optimization pass in the compiler of Racket, one of the problem is that enabling debugging kills many of the optimizations. So when debugging is enabled the problem disappears.
Another problem is that it has a lot of expansion and passes, and some of the code is in Chez Scheme. So when modifying the code in Chez Scheme that is used to compile itself and later to compile the code in Racket, it is difficult to run all of these in a debugger.
And when an optimization is wrong, it's like if the compiler sees a code that is not what you are seeing, so the error may appear in a weird place and perhaps far away from the wrong code.
[1] I still miss stop-edit-and-continue that was available in Classic Visual Basic 6. And IIRC QuickBasic has an option to see a few of the previous instructions before the breakpoint...