Author | Topic: Re: XppFatal | |
---|---|---|
Andreas Gehrs-Pahl View the complete thread for this message in: | Re: XppFatal on Wed, 07 Jan 2015 14:32:59 -0500 Carlos, >Can anyone tell me, please, what the error below mean besides that the >application interrupted suddenly? >FATAL ERROR LOG >No continue after this Error! >SYS Thread-ID: 336 >Module: EXE >Error Codes: EH: 10 Sub: 0(0) OS: 0 XPP: 0 >Call Stack of Thread 1 (336): ><non constant name>(944) >Call Stack of GUI Thread (520): >Call Stack of Thread 3 (1800): >File: Z:\Mantis\MSIFiles\Runtime\VSrep01\Pointer_.exe >TimeStamp: 20150106 13:13 >End of FATAL ERROR LOG. The XppFatal Error log shows that the (call) stack of your application has been corrupted, probably by inadvertently overwriting some of the stack. This can happen if external libraries -- such as OT4XB or other DLLs -- that you call in your code misbehave or are called incorrectly. The Xbase++ SubSystem-Error Code of "10" (EH) supposedly means: "The result of the Error Handler CodeBlock allows no continue after this operation", and is only seen in XppFatal Error logs. The "<non constant name>" text is shown when the actual procedure, function, or method name can't be determined, due to the stack corruption. The only other information that is available is that the error occurred in your Main Thread (with Thread ID 336) in the Expression Executer Module of the Xbase++ runtime ("Module: EXE"). Hope that helps somewhat, Andreas Andreas Gehrs-Pahl Absolute Software, LLC phone: (989) 723-9927 email: Andreas.GP@Charter.net web: http://www.Aerospace-History.net |