4 ms·
When I used to work on Win9x, where badly-behaved programs would often corrupt memory and lead to the system eventually crashing, I made use of that trick a few
by userbinator 6y ago
When I used to work on Win9x, where badly-behaved programs would often corrupt memory and lead to the system eventually crashing, I made use of that trick a few times --- keeping a kernel debugger resident meant that sometimes I could skip over faulting code and keep the OS alive long enough to save/finish my work and reboot. But often, a lot of things would stop working too, which is not so surprising since if you continue to ignore errors you will eventually end up with an empty program.
Also reminds me of this: https://news.ycombinator.com/item?id=4157777 https://news.ycombinator.com/item?id=4157777
- staycoolboy 6y agoDid you ever use BlackICE? I worked on Windows drivers in the early 90's and all of our systems had BlackICE running which was like a hypervisor debugger with full hardware control: you could CTRL-ALT-TAB into it and halt the OS at any point and save state. The basic debug strategy was to break to BlackICE on fault, handle it with a macro, and save the OS from crashing. Super useful, also great for breaking copy protection on games. ;-)
- trasz 6y agoWasn't that SoftIce?
- KeBugCheckEx 6y agoSurely SoftICE.
- staycoolboy 6y agoWow, yes it was. I have no idea where BlackICE came from in my mind... Thanks!
- pantalaimon 6y ago> I have no idea where BlackICE came from in my mind... Sounds like something from Neuromancer
- gjvc 6y ago"BlackICE Defender" was a popular Windows firewall.
- userbinator 6y agoSoftICE, yes, I used that one.
- abbeyj 6y agoI think that this was the idea behind Norton CrashGuard. Intercept all faults and then try to skip past the faulting instruction. This worked ... sometimes. At least long enough for you to save your work and restart the program. But lots of times you'd get stuck in an endless loop or end up locking up the whole system anyway.