Advertisement

Invalid Page Fault?

Started by June 29, 2000 05:49 PM
3 comments, last by Esap1 24 years, 5 months ago
My program caused an invalid page fault in kernel32.dll, what does that mean?
depends on what you are trying to do.
To the vast majority of mankind, nothing is more agreeable than to escape the need for mental exertion... To most people, nothing is more troublesome than the effort of thinking.
Advertisement
I mean generaly what is a page fault. An Access Violation is when you try to access memory thats not yours, whats a page Fault(and what does it mean when its in Kernel32.Dll?).
A page fault means your program accessed a page that did not have an entry in its page table (hence, the page is invalid.) It''s similar to an access violation, basically, "you used a bad pointer."

Because it occurred in Kernel32.dll, it means you either passed an invalid pointer to a kernel32 function, or you corrupted data structures in your process which kernel32.dll depends on (like you''re process heap.)
quote: Original post by mhkrause

A page fault means your program accessed a page that did not have an entry in its page table (hence, the page is invalid.) It''s similar to an access violation, basically, "you used a bad pointer."

Because it occurred in Kernel32.dll, it means you either passed an invalid pointer to a kernel32 function, or you corrupted data structures in your process which kernel32.dll depends on (like you''re process heap.)



Well, UnhandledExceptionFilter reports certain access violations as IPFs. I think it happens when your process tries to access memory in a read-only page in an image file, but I could be wrong. Why not give the debugger a poke?
VK

This topic is closed to new replies.

Advertisement