debugger crash log
DOCX · 16.4 KB
Open DOCX file
A brief working note, apparently written by Phil, recording a series of file-copy tests (phil1 through phil8) to isolate why the Maple debugger crashed. Removing content below the working area stopped the crashes, while renaming variables, commenting out code, or replacing it with text did not. The note concludes that nothing may be present in the worksheet below the point being debugged.
AI-written summary; may contain errors.
Extracted text (machine-read; may contain errors)
Maple debugger Debug! PhL 2.10.03
The thing is intermittent, so we have to be rigorous in leaving a file trail:
The original file fails, I made a copy of it called phil1, so phil1 fails.
cut comments from the top, remove code at bottom, call this phil2. It does NOT crash!
start again with phil1, make sure it still crashes. Yes, it does.
Only cut the text from top of phil1, make that phil3. This phil3 crashes.
Only cut away stuff from the bottom of phil1, make that phil4. Then phil4 does NOT crash.
Start again with phil1, change n and m in the bottom code to nn and mm, save as phil5. Crashes!
It seems that having ANY code below your working area kills you?
Leave the below-code all there, but comment out every line of it, save as phil6. Crashes.
Replace the below-code with just a text comment save as phil7. Crashes.
Repeat earlier experiment. Start with phil1, remove all bottom stuff, call it phil8 this time.
Conclusion: When you are debugging, you cannot have anything at all in the worksheet below the place at which you are working!