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. ;-)
[ Parent
| on HN ]
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.