C++ Builder IDE >> R: R: R: R: R: R: R: Internal Compiler Error

by Somebody » Fri, 05 Aug 2005 01:32:35 GMT


> 1. Do your development under the Builder with no service pack. I don't
> understand why your boss can't live without it.

Tell it to Him !!!

> 2. Compile the .cpp that fails under the Builder with no service pack,
> save the .obj file and do the final build under the Builder with the
> service pack.

That's what I 've done !!!

> 3. As recommended by Andrue, try commenting out the code in the function
> you provided line by line until the "internal compiler error" disappears
> (do it under the Builder with service pack). The last line commented
> would probably be the code that causes the error and you should change
> it with something else.

shouldn't the error be at the line pointed by the compiler ?
it says the line 603 which is the end of file, no instruction there is, look
at some post ago !
However I've tried by commenting all the methods, all in one , but always
the same error and before giving the
error which say "class not found" or things like that






C++ Builder IDE >> R: R: R: R: R: R: R: Internal Compiler Error

by Somebody » Fri, 05 Aug 2005 08:34:25 GMT


We don't want get you work hard in our code, but as we detected the error
and mainly because we are not in company seeing that we are in vacation (we
test it by sending each other code once a day and in different computer !).

can we send the code to you ? we have no problem !
it's enought compile whitout obj file and with the service pack included !

should it be possible, you would make us a big favor !
I think that'is much more hard chatting whit each other than check it by
yourself who are
much more expert than us !

Please !



42f25583$ XXXX@XXXXX.COM ...
always





C++ Builder IDE >> R: R: R: R: R: R: R: Internal Compiler Error

by Muzaffar Mahkamov » Fri, 05 Aug 2005 16:14:15 GMT

Well, Borland compiler sometimes points at a very different location
than the place the error was actually encountered. I faced this problem
several times and it's very frustrating since you need to find the error
manually.

Try enabling "Extended error information" in Project->Options->Compiler.
That might give you a better clue of what's happening with the compiler.
You'll see a "full parser context" in the build output.




R: R: R: R: R: R: R: Internal Compiler Error

by Andrue Cope [TeamB] » Fri, 05 Aug 2005 17:29:25 GMT





This seems to happen to me when I'm making changes to headers in the
precompilation list. It can be very irritating.

--
Andrue Cope [TeamB]
[Bicester, Uk]
http://info.borland.com/newsgroups/guide.html


Similar Threads

1. Possible VS2003 c# compiler bug: error CS0584: Internal Compiler Error: stage 'COMPILE' symbol ''

Hi everybody!

It's the second time it happens to me... Working with typed DataSets
and doing copy & paste, I compile and get weirds messages like these:

An internal error has occurred in the compiler. To work around this
problem, try simplifying or changing the program near the locations
listed below. Locations at the top of the list are closer to the point
at which the internal error occurred.

error CS0584: Internal Compiler Error: stage 'BIND' symbol
'WindowsApplication1.Form1.Form1_Load(object, System.EventArgs)'
error CS0584: Internal Compiler Error: stage 'COMPILE' symbol
'WindowsApplication1.Form1'
error CS0584: Internal Compiler Error: stage 'COMPILE' symbol
'WindowsApplication1'
error CS0584: Internal Compiler Error: stage 'COMPILE' symbol ''
error CS0586: Internal Compiler Error: stage 'COMPILE'

Once you get one of these you must exit VS2003, because the compiler
does not work anymore...

Here is how to reproduce it:

Create a Solution, with 2 projects, one client app and one class
library.

In the class library proyect add a typed Dataset, and a class with a
method like this:

public MyDataset FakeFunction (MyDataset.ClassificationDataTable table)

{
  return new MyDataset();
}

In the client app, call the method in this way (here's where the error
is):

MyDataset ds2 = MyClass.FakeFunction(ds.ClassificationDataTable);

That is you miss it doing copy-paste, you should have written:

MyDataset ds2 = MyClass.FakeFunction(ds.Classification);

And you got the evil messages, very descriptive, aren't they?

The curious thing about it is that if you place the class with the
method and the Dataset in the client app proyect, the error message is
accourate, so the error only happens when referencing another project:

error CS0572: 'ClassificationDataTable': cannot reference a type
through an expression; try
'ClassLibrary1.MyDataset.ClassificationDataTable' instead

2. Template specialization, default args, typedef and an internal compiler error

3. Functions with ellipsis arguments in templates : Internal Compiler Error VC++ .Net 2002 edition

Hello Everyone,

The code that I will append to this message generates an internal
compiler error on my install of VC++ .Net 2002.

The code looks OK to me, although that doesn't necessarily prove
anything. ;-)

I couldn't find a reference to this problem in the KnowledgeBase, so I
was wondering if one of you could confirm that this is indeed a
problem with the compiler, and if there is a work-around.

Thanks in advance,

Peter Dulimov.


-----8<--------------------8<-----------------8<---------------

#include <map>
#include <algorithm>

namespace Utility
{
  template <class container>
    class CDestroyer  
    {
    public:

      typedef typename container::value_type TVal;

    private:

      template <typename T>
        class ClassOf
        {
            typedef T OriginalType;
        };

      template <typename t3>
        void KillKey(const t3 * const ptr) const
        {
          t3 * p = const_cast<t3 *>(ptr);
          delete p;
        }

      void KillKey(...) const
      {
      }

      void DoIt(const TVal& stored, ...) const
      {
          delete stored;
      }

      template <typename t1, typename t2>
        void DoIt(const TVal& stored, ClassOf<std::pair<t1, t2> >)
const
        {
          KillKey(stored.first);
          KillKey(stored.second);
        }

    public:

      void operator()(const TVal& stored) const
      {
        DoIt(stored, ClassOf<TVal>());
      }
    };
}

class CFrobNatz;

class CCarrot
{
  typedef std::map<int, CFrobNatz *> MapType;
  MapType m_problem;

public:
  CCarrot(int t);

  virtual ~CCarrot()
  {
    std::for_each(m_problem.begin(), m_problem.end(),
Utility::CDestroyer<MapType>());
  }
};

class CFrobNatz
{
public:
  int m_number;
};

CCarrot::CCarrot(int t)
{
  for (int i = 0; i < t; ++i)
  {
    m_problem.insert(MapType::value_type(i, new CFrobNatz));
  }
}

int main()
{
  CCarrot data(5);

  return 0;
}

4. My compilation died with what it called an internal compiler error

5. [C++ Fatal Error] Math.hpp(81): F1004 Internal compiler error

Hello,

when I compile my component-package, I get this error message. After
compiling again, no error occurs. I don't use Math directly and I have
never had that problem before.

[C++ Fatal Error] Math.hpp(81): F1004 Internal compiler error at 0x129d547 with 
base 0x1200000

//-- var, const, procedure ---------------------------------------------------
    static const Extended MinSingle = 1.500000E-45;
    static const Extended MaxSingle = 3.400000E+38;
    static const Extended MinDouble = 5.000000E-324;
    static const Extended MaxDouble = 1.700000E+308;
    static const Extended MinExtended = 3.400000E-4932;
-> static const Extended MaxExtended = 1.100000E+4932;
    static const Extended MinComp = -9.223372E+18;
    static const Extended MaxComp = 9.223372E+18;

The problem seems to be the line marked with "->".
Any hint?


Thanks and greetings
Udo

6. [C++ Fatal Error] SHDocVw_OCX.h(1202): F1004 Internal compiler error at 0x127e674 with base 0x1200000 - Borland C++ Builder VCL Components

7. R: R: R: R: R: R: Internal Compiler Error

Let's summarize:

1) without service pack it works anyway
2) with service pack it works only if file Obj already exist, I mean after
having installed BCP5 without service pack and once compiled the code and
created the file Obj and installed the service pack, it works. If we delete
the obj file with the service pack included and try to compile it doesn't.

we think it has to do just with the Obj file, in fact the error line is the
end of the file, no instruction there is, have a look at some post ago.

BUT now I m wondering, why on building time the compiler was quiet ?


8. fatal error C1001: INTERNAL COMPILER ERROR (compiler file 'f: