Thread overview |
---|
April 12, 2005 InternalError: eh 684 | ||||
---|---|---|---|---|
| ||||
While compiling a file, I get: Internal Error: eh 684 1. Not sure how to find out exactly what "eh 684" means. 2. According to this post http://www.digitalmars.com/archives/cplusplus/3974.html it appears to be a compiler out of memory problem. Is this ture? So, I've tried setting switch -HPnn up to -HP220, but still get the same error (I would think 220 MB would be enough) Is eh 684 a compiler memory problem, and should -HPnn switch be fixing the problem? WinME 184 MB RAM - sad, but true Thanks, Doug |
April 12, 2005 Re: InternalError: eh 684 | ||||
---|---|---|---|---|
| ||||
Posted in reply to dt | In article <d3fqqp$1rc2$1@digitaldaemon.com>, dt says... > >While compiling a file, I get: > >Internal Error: eh 684 > >1. Not sure how to find out exactly what "eh 684" means. > >2. According to this post http://www.digitalmars.com/archives/cplusplus/3974.html it appears to be a compiler out of memory problem. Is this ture? > >So, I've tried setting switch -HPnn up to -HP220, but still get the same error (I would think 220 MB would be enough) > >Is eh 684 a compiler memory problem, and should -HPnn switch be fixing the problem? > >WinME >184 MB RAM - sad, but true > Well, I think you should post the code that digital mars having internal error when compiling it. |
April 12, 2005 Re: InternalError: eh 684 | ||||
---|---|---|---|---|
| ||||
Posted in reply to Jack | "Jack" <Jack_member@pathlink.com> wrote in message news:d3fr60$1rk0$1@digitaldaemon.com... > In article <d3fqqp$1rc2$1@digitaldaemon.com>, dt says... > > > >While compiling a file, I get: > > > >Internal Error: eh 684 > > > > Well, I think you should post the code that digital mars having internal error > when compiling it. > Hi Jack, It will be rather lengthy because of abundant includes. It will take me some time to dig a little deeper, and post only minimal code. But, looking at verbose output, I discovered something that is surely a problem, in some templated code. It appears that somewhere the names of classes are getting screwed, for the class VCF::ObjectWithEvents, as seen below. This appears in the verbose output during compile: VCF::ClassInfo<CF::VObjectWithEvents::CF >::isClassRegistered Notice the "<CF::VObjectWithEvents::CF >" There is no namespace nor class CF, nor a class VObjectWithEvents. However, there is a class VCF::ObjectWithEvents. I have searched through the files for a programmer typo that may cause this, but have not found any yet (so perhaps the toolchain is screwing it up). MSVC6, VC7.0, VC7.1, BCC5.5, BCB6, CW9, icl7, and gcc on OSX all compile/build this library without any problems. I'll dig deeper tonight. Thanks. > |
April 14, 2005 Re: InternalError: eh 684 | ||||
---|---|---|---|---|
| ||||
Posted in reply to dt | "dt" <tinkham@ucalgary.ca> wrote in message news:d3grae$2t75$1@digitaldaemon.com... > > "Jack" <Jack_member@pathlink.com> wrote in message news:d3fr60$1rk0$1@digitaldaemon.com... > > In article <d3fqqp$1rc2$1@digitaldaemon.com>, dt says... > > > > > >While compiling a file, I get: > > > > > >Internal Error: eh 684 > > > > > > > Well, I think you should post the code that digital mars having internal > error > > when compiling it. > > > > Hi Jack, > It will be rather lengthy because of abundant includes. It will take me some > time to dig a little deeper, and post only minimal code. Ok, I followed the instructions on bug reporting, and incrementally commented out code until I narrowed it down. It turns out that in one of my several hundred classes, there was not a constructor defined. So, I defined an empty constructur, and Internal Error disappeared. I don't see anything in the class that would absolutely require a constructor to be defined. Would this still be considered a compiler bug, that I should report? Doug |
April 14, 2005 Re: InternalError: eh 684 | ||||
---|---|---|---|---|
| ||||
Posted in reply to dt | "dt" <tinkham@ucalgary.ca> wrote in message news:d3mrfj$1utu$1@digitaldaemon.com... > Ok, I followed the instructions on bug reporting, and incrementally commented > out code until I narrowed it down. It turns out that in one of my several hundred classes, there was not a constructor defined. So, I defined an empty > constructur, and Internal Error disappeared. I don't see anything in the class that would absolutely require a constructor to be defined. Would this > still be considered a compiler bug, that I should report? Internal errors are always compiler bugs. Please send me a sample that reproduces it, so it can get fixed. Thanks, -Walter |
April 19, 2005 Re: InternalError: eh 684 | ||||
---|---|---|---|---|
| ||||
Posted in reply to Walter |
"Walter" <newshound@digitalmars.com> wrote in message >
> Internal errors are always compiler bugs. Please send me a sample that reproduces it, so it can get fixed. Thanks, -Walter
Walter,
I haven't forgotten about this, but am having difficulty getting it narrowed
down.
I thought I would try to just make a listing file to get it all in 1 file
for you, but
when the listing file reaches about 2.1 MB (there are quite a few comments),
the
output just cuts off. I can't figure out how to get listing file without
comments, and
not even sure that would help. I'll slowly work on getting the error with
less code.
Doug
|
Copyright © 1999-2021 by the D Language Foundation