Re: Re:Debugging in the device-kernel
- From: "Skywing" <skywing_NO_SPAM_@xxxxxxxxxxxxxxxxxxx>
- Date: Sun, 9 Apr 2006 22:26:25 -0400
But the point is, you have no way of knowing whether a bug in your driver
(or even hardware) will cause something to get damaged that is necessary for
say filesystem or disk or registry operation. They all run in the same
kernel memory space.
This is why I say you have just been lucky (or perhaps not unlucky) so far.
Believe it or not, these kinds of things do actually happen and do actually
cause installs to get corrupted in the real world, even if you are just
doing something that might appear to be unrelated. (Maybe you overrun a
pool allocation into some memory owned by Ntfs, for example.)
"anton bassov" <xxx@xxxxxxx> wrote in message
news:de1fd7e86e96471895527536e3befee4@xxxxxxxxxxxxxx
Well, it depends on what you are doing.... I would say that, unless the
crash is caused by some operation that involves hard disk
(file,registry,etc)
, you can safely reboot, without causing any persistent damage to the
system
Regards
Anton Bassov
.
- Follow-Ups:
- Re: Re:Debugging in the device-kernel
- From: anton bassov
- Re: Re:Debugging in the device-kernel
- References:
- Re: Re:Debugging in the device-kernel
- From: Skywing
- Re: Re:Debugging in the device-kernel
- From: anton bassov
- Re: Re:Debugging in the device-kernel
- Prev by Date: Re: Re:Debugging in the device-kernel
- Next by Date: Re: Re:Debugging in the device-kernel
- Previous by thread: Re: Re:Debugging in the device-kernel
- Next by thread: Re: Re:Debugging in the device-kernel
- Index(es):
Relevant Pages
|