A
Alain Dekker
Apart from malicious software (eg. virus) or a device driver (which has
access to the kernel layer), is it possible for a standard application
written in C++ / C#.NET / VB / Delphi / etc to crash and/or corrupt Windows
XP?
We had one report from a customer who said that due to an accidental coding
bug, they saw a "divide by zero" error which not only crashed our software
but immediately afterwards Windows rebooted and then failed to restarted
(kept locking up and rebooting).
If the report is accurate, can user mode level programs do this? Is there
any way to prevent this?
As a final note, I reproduced the "dive by zero" crash and fixed it.
Certainly didn't crash my computer, though. In fact, I've never seen Windows
XP do what is reported here.
Thanks,
Alain
access to the kernel layer), is it possible for a standard application
written in C++ / C#.NET / VB / Delphi / etc to crash and/or corrupt Windows
XP?
We had one report from a customer who said that due to an accidental coding
bug, they saw a "divide by zero" error which not only crashed our software
but immediately afterwards Windows rebooted and then failed to restarted
(kept locking up and rebooting).
If the report is accurate, can user mode level programs do this? Is there
any way to prevent this?
As a final note, I reproduced the "dive by zero" crash and fixed it.
Certainly didn't crash my computer, though. In fact, I've never seen Windows
XP do what is reported here.
Thanks,
Alain