3 ms·
>Press keys. Nothing happens. Hours pass. Realize interrupts are turned off and I need to turn them on. >THE OS IS STILL CRASHING WHEN I PRESS A KEY. This cont
by unfamiliar 13y ago
>Press keys. Nothing happens. Hours pass. Realize interrupts are turned off and I need to turn them on.
>THE OS IS STILL CRASHING WHEN I PRESS A KEY. This continues for 2 days. Remember that now that I have remapped interrupt 1 to interrupt 33 and I need to update my IDT.
I have issues like this a lot (i.e. forgetting I've tweaked something and wondering what is causing weird effects). Any advice on how to avoid it?
- zenojevski 13y agoUse a rubberducking text file. Every time you think, write down a line or two delineating your current reasoning and your debugging info. When you make changes, highlight them to mark them as pending ("need to update IDT"). You can also categorize, tag lines/pieces, and so on. When you're stuck just backtrack this file, whether it is a hour or two days from now, and you'll avoid all of this.
- exDM69 13y ago> I have issues like this a lot (i.e. forgetting I've tweaked something and wondering what is causing weird effects). Any advice on how to avoid it? Use your version control, commit more often and use more descriptive commit messages, along with branching/merging strategies to avoid putting not-production-ready code you are unsure of to master.
- maaaats 13y agoCommit before changing stuff. Easy to roll back, and to see what changes you have done lately.