Click to See Complete Forum and Search --> : Access Violation


Dave E.
May 21st, 1999, 01:42 PM
At work I have NT4.0 and at home I have Win98. My application runs fine at work but at home my app crashes -- "Access Violation". This is what I get:
FIRESIMSG caused an invalid page fault in
module MAPD.DLL at 015f:00733ec8.
Registers:
EAX=014eae8c CS=015f EIP=00733ec8 EFLGS=00010202
EBX=014eb1ca SS=0167 ESP=014eae10 EBP=014eaea0
ECX=00000000 DS=0167 ESI=014eaeac FS=4f77
EDX=02341e00 ES=0167 EDI=014eaf50 GS=0000
Bytes at CS:EIP:
8b 51 1c 8b 45 f0 8b 48 1c 8b 01 52 ff 50 44 85
Stack dump:
014eae8c 014eaf50 014eaeac 014eb1ca ffffffff 02345a60 02345a64 00000000
014eae40 00520fe1 00000001 00000000 014eae54 005250da 00000001 02340300

MSDN says --
There are four basic kinds of actions that can cause access violations:

· Attempting an invalid operation, such as writing to a read-only page

· Attempting to access memory beyond the limit of the current program’s
address space (a.k.a. “length violation”)

· Attempting to access a page to which the system forbids access

For example, code is not allowed to run in the low-order 64K of the NT
user-mode address space in order to simplify the detection of NULL pointer
references.

· Attempting to access a page that is currently resident but dedicated to the
use of an NT component

But since the app runs fine on my NT machine I'm at a loss as what to do next. The MAPD.DLL is part of my project.

Thanks.


"The hardest thing in the world to understand is the income tax." - Albert Einstein