paxmania.blogg.se

That would indicate that one of the xml files that ship with FSX, e.g.:Īre not what the parser expects or perhaps a version compatibility with something in the OS that their parser uses. I get the impression, looking at the stack traces, that simprop.dll is a re-invented XML parser (a so called "AceParser"). The code inTheCrashingCall already detectsnull` argument and does nothing: simprop.TheCrashingCall(Arg1) What i have been able to do, is modify simprop.dll, so that if Arg1 is is invalid, then make it null. and the code never checks that 30 is null Later on we will try to access that address. Return eax+8 //this is the source of the invalid 0x08 value Trying to reverse engineer the code, i come up with: simprop.20C4A6A0(Arg1, Arg2, Arg3, Arg4)Įax = Arg2.Method10(Arg2) //Method10 returns 0x08, the source of the AVĮax = TheCrashingCall(eax) //pass the bad addressĮax = ecx+30^ //eax+30^ is nil (i.e. It crashes with an access violation (error code 0xc0000005) trying to read address 0x00000008. When it tries to do the compare: cmp ecx, The problem is that edi points to address 0x08.

Running FSX under a debugger shows me the actual problem: *** ERROR: Symbol file could not be found. The audit log shows cursory error details, an access violation (Error code C0000005) in simprop.dll. The error i'm getting is extraordinarily common (Bing for simprop c0000005). Windows 8 Pro with Media Center, 64-bit.i've been trying to get a crash dump, so i can start to debug it, but getting a crash dump in Windows 8 is an extraordinary pain.tried running as an Administrator (i.e.tried running with Windows XP, and Windows 7 compatibility modes.Does anyone know if this is a known issue under Windows 8?.Has anyone fixed the error under Windows 8?.