What is EEDFACE ??

External Exception EEDFACE

Happens when loadding a dll.

Does anybody knows what this exception means?
Is this a Delphi Exception??

Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Look in the Delphi help under $FEEDFACE, if I can remember rightly, I think it means that your DLL threw an unhandled exception (usually a memory allocation problem in your DLL code)

Right, I had a look (it is actually under $0EEDFACE), and basically, if your application or DLL is not written in Object Pascal (Delphi) and it throws an exception, then Win32 does not know how to handle it, so you get an EEDFACE exception.

Hope this helps...

mferdockAuthor Commented:
I could not find 0EEDFACE or FEEDFACE
in the Delphi 4.0 help file. Where would
it be found.
Also, could this exception be created if you called a DLL written in Delphi 2.0 from an application that is written
in delphi 4.0 ?

The following is from D3 C/S Help:
If an exception is raised but not handled in a DLL, the exception is propagated out of the DLL. If the calling application or DLL is itself written in Delphi, it is possible to handle the exception through a normal try...except statement.
If the calling application or DLL is written in another programming language, the exception can be handled as an operating system exception with an exception code of $0EEDFACE. The first entry in the ExceptionInformation array of the operating system exception record contains the exception address, and the second entry contains a reference to the Delphi exception object.

If a DLL does not use the SysUtils unit, Delphi's exception support is disabled. In that case, if a runtime error occurs in a DLL, the application that called the DLL terminates. Because a DLL has no way of knowing whether it was called from an Object Pascal application or an application written in another programming language, it is not possible for the DLL to invoke the application's exit procedures before the application is terminated. The application is simply aborted and removed from memory. For this reason, make sure that there are sufficient checks in any DLL code so such errors do not occur.
Regards, Geo

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.