From: Keith M. <kei...@us...> - 2008-08-01 21:09:22
|
On Friday 01 August 2008 00:10:39 Brian Dessent wrote: > This particular family of faults is particularly vexing because it's > an access violation generated by the operating system loader (NTLDR) > during the process of loading the program's image into memory and > applying any relocs, before the process has even executed a single > instruction of its own. This means you can't really even use a > debugger to figure out what's going on other than to retrieve the > status code. Sure. Your point is that there are a number of circumstances, during process start-up, which may result in an access violation, and which are not addressed by the patch mentioned earlier in this thread; that's certainly a perfectly reasonable point to make. My point, however, is that there are other possible circumstances in which this same exception will be raised; many, if not even a majority of those, will be attributable to bugs in the user's own code. Regards, Keith. |