Again, you’re right, it shouldn’t happen. But it’s a house of cards built on
a poor foundation.
The user shouldn’t be backspacing passed the end of his/her/its buffer. It’s
brain dead code. I would spend my time fixing the app, reporting my findings
to MS, and then booting any developer in the butt that worked for me if I
see him/her/it writing code like that.
Gary G. Little
Staff Engineer
Broadband Storage, Inc.
xxxxx@broadstor.com
-----Original Message-----
From: xxxxx@myndos.com [mailto:xxxxx@myndos.com]
Sent: Tuesday, October 30, 2001 5:00 PM
To: NT Developers Interest List
Subject: [ntdev] Re: [windev] Did you know?? BSOD - Blue Screen of Dea- th -
very si mple
The very odd thing is that it doesn’t seem to crash if you single step
through the code using a debugger. Yet there are no signs of a first
chance exception or anything of the sort in the output window.
I’m quite puzzled. Could it be that the CSRSS is not actually ‘crashing’,
but simply poorly handling an error condition (ie… just being lazy)? (I
say this because I’m surprised a single character underflow would be so
catastrophic).
Anyone see any fix for this yet?
Memet
You are currently subscribed to ntdev as: xxxxx@broadstor.com
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
You are currently subscribed to ntdev as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com