Johan
Johan

Reputation: 76577

How to decode internal errors and probable causes?

I've been typing for a long time to get compilable code.
Because I'm implementing an interface with quite a lot of members.

Halfway though the process I have something that compiles, but now XE2 strikes me with an internal error:

[DCC Fatal Error] F2084 Internal Error: L2095

Problem is that it's hard to rewind, because the last time I had compilable code was when I had 2000 fewer lines.

Is there a way to decode the internal error so that I have an inkling of that's causing the compiler to break down?

Note that I did not tag this question XE2, because the issue of internal errors is not limited to this version

Upvotes: 1

Views: 680

Answers (1)

Rudy Velthuis
Rudy Velthuis

Reputation: 28806

Internal errors are errors in the compiler or linker. The codes you get, like L2095, have no meaning for us users. They only have meaning for those who actually write the compiler and linker, i.e. for the developers at Embarcadero.

FWIW, I've been told the number is a hint where exactly the error occurs (line number?), and the letter in which part of the compiler/linker combo. Not useful for us mere mortals, though, sorry.

And before you ask: I don't know of a comprehensive list of internal errors and how to avoid or work around them. You could google them, or look in QC if yours is mentioned and if there is a workaround.

Update

See Andrei Galatyn's comment and the link in there for some help on resolving internal errors.

Upvotes: 3

Related Questions