|2055F408|dbkdebugide120.bpl |Debug.pas |TProcess |LinkUnitCreated |8453 | |2055F40F|dbkdebugide120.bpl |Debug.pas |TProcess |LinkUnitCreated |8454 | |219C5BDA|win32debugide120.bpl|Win32Debug.pas |TWin32LinkUnit |GetCppDebugHook |1923 | |777DE550|ntdll.dll | | |RtlEnterCriticalSection | | |03DBC436|dcc120.dll |BROWCMGR.OBJ | |GetNearestSymName | | |03DBBF70|dcc120.dll |BROWCMGR.OBJ | |PutToAddress | | |777DE590|ntdll.dll | | |RtlLeaveCriticalSection | | |03DE8D30|dcc120.dll |DECL.OBJ | |PatchConstRecordParameter | | |03E30D6C|dcc120.dll |SYMTAB.OBJ | |FindBaseClassMethod | | |03E3064C|dcc120.dll |SYMTAB.OBJ | |MakeOverloadedPropertyList| | |03E3066D|dcc120.dll |SYMTAB.OBJ | |MakeOverloadedPropertyList| | |777DE49A|ntdll.dll | | |KiUserExceptionDispatcher | | |Running Thread: ID=5068 Priority=0 Class= | |Address |Module |Unit |Class |Procedure/Method |Line | The Error is trapped for me by EurekaLog, and the error report gives the following call stack: Call Stack Information: I also have IDE Fix Pack 2009 2.9 installed. I have all the Delphi 2009 Updates installed right up to and including Update 4. Of course, if I was unable to SaveAll, then I lose all the edits I had made since last saving. ![]() Either way I am stuck and then the only thing I can do is use Windows Task Manager to shut down Delphi. If I am lucky I can sometimes do a File/SaveAll in Delphi, but sometimes I can't. This only happens occasionally, but after pressing OK, then my IDE and program both may freeze. While debugging my application with Delphi 2009, I sometimes get the following exception occurring: It seems that "External exception" isn't a Delphi's bug, I had this exception times ago and it was probably a problem with the motherboard, or with the hardware, because the program worked well at other machine. The splash screen to my applications do not appear now when I'm debugging but at least I don't get that EEFFACE error anymore. When I create and access the splash screen. So to overcome this issue, I now put if DebugHook = 0 then I tried various other ways to do splash screens but they always eventually resulted in getting an EEFFACE error when debugging. I could put a break point on the first line of the dpr file and found that it always seemed to occur when creating the splash screen to my applications. ![]() The same code never received that error message on Windows XP. I received this error regularly when I went to Windows Vista and 7. This is not an exact answer but may help you with overcoming the error by describing my experience with it. When the exception code is not a Delphi generated exception or a hardware related exception, Delphi simply maps it to EExternalException. ![]() If you can reproduce this with a test case, please report it in Qualit圜entral ( ).ĮEFFACE is the SEH exception code used by C++, which is "leaking" out to some Delphi code (in this case the IDE itself). The odd thing is that if it is, in fact, going through writeobj.c, something is certainly not quite right. This is clearly something happening in the Delphi evaluator (which is part of the compiler).
0 Comments
Leave a Reply. |