News for hackers. Stuff that matters.
Re:Why is there a “V” in SIGSEGV Segmentation Fault? by userbinator on Thursday June 18, 2020 @09:43AM (#23563018)
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

Re:Why is there a “V” in SIGSEGV Segmentation Fault? by staycoolboy on Thursday June 18, 2020 @12:43PM (#23564905)
Did 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. ;-)
Re:Why is there a “V” in SIGSEGV Segmentation Fault? by trasz on Thursday June 18, 2020 @01:02PM (#23565112)
Wasn't that SoftIce?
Re:Why is there a “V” in SIGSEGV Segmentation Fault? by staycoolboy on Thursday June 18, 2020 @02:25PM (#23566035)
Wow, yes it was. I have no idea where BlackICE came from in my mind... Thanks!
Re:Why is there a “V” in SIGSEGV Segmentation Fault? by pantalaimon on Thursday June 18, 2020 @02:34PM (#23566138)
> I have no idea where BlackICE came from in my mind...

Sounds like something from Neuromancer

Re:Why is there a “V” in SIGSEGV Segmentation Fault? by gjvc on Thursday June 18, 2020 @09:06PM (#23569966)
"BlackICE Defender" was a popular Windows firewall.
Re:Why is there a “V” in SIGSEGV Segmentation Fault? by KeBugCheckEx on Thursday June 18, 2020 @01:11PM (#23565203)
Surely SoftICE.
Re:Why is there a “V” in SIGSEGV Segmentation Fault? by userbinator on Thursday June 18, 2020 @08:19PM (#23569653)
SoftICE, yes, I used that one.
Re:Why is there a “V” in SIGSEGV Segmentation Fault? by abbeyj on Thursday June 18, 2020 @02:05PM (#23565804)
I 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.