Re: VB Application compilation Error.. urgent

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

"harry" <harry@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:5FBDA222-FF0A-4104-9ED5-D52C73089676@xxxxxxxxxxxxxxxx

We faced following error while compiling visual basic 6 project
C:\EPOS(SIS)\CData\clsDocumentShow.cls(-184) : fatal error C1001: INTERNAL
COMPILER ERROR
(compiler file 'E:\8783\vc98\p2\src\P2\coff.c', line 1371)
I reinstalled the visual studio with new service pack but still same error


On Google I found the same question repeated many times but only one posting
that looked like a possible answer.  I couldn't find any confirmation of
whether the possible answer worked for the victim in that case.  If you try
this, please post and say if it works.  Then maybe future searches on Google
will include the answer!

This is the only possibility I found:
===
Newsgroups: microsoft.public.vb.general.discussion
From: "Ralph" <msnews.20.nt_consultin...@spamgourme­t.com>
Date: Fri, 24 Sep 2004 22:17:09 -0500
Subject: Re: VB6 started to mess up...

"Mika Kokko" <mika.ko...@removeme-aboa-ohje­lmistot.com> wrote in message
news:cj10js$er9$1@xxxxxxxxxxxxxxxxxxxxxxxxx

E:\project\form129.frm(1233) : fatal error C1001: INTERNAL COMPILER ERROR
  (compiler file 'E:\8783\vc98\p2\src\P2\main.c­', line 494)


[My guess the problem has gone away by now. <g>]

This error is coming from the "c2" compiler which is essentially the same
phase 2 compiler that is used for compiling C/C++ programs. In C++ the
error 'usually' is caused (assuming you don't have a corrupt C2.exe) by
mismatched pch and incremental obj files. I said 'usually' because the
exact cause is often difficult to ascertain - it is the eqvalent of "I
have fallen and can't get up".

The repair is to simply remove all intermediate files and do a clean
re-compile. It often just goes away on its own.

Try doing the same with your VB application. Remove everything but the
source files(saving .exe and .dll for binary compatiblity) and re-compile,
skipping any 'groups' you might have, each project independently.

It always possible that the file (form/class) that is reporting the error
may have something wrong with it, but usually the point at which the
compiler 'bails' is far removed from where the actual erroneous code is
located. I would still make sure the code in the form is clean and doesn't
have strange (poorly matched) conditional directives (#IF...), exteme
lengths, creative switches, etc. <g>

hth
-ralph


.

Relevant Pages

  • Re: Internal compiler error problem
    ... INTERNAL COMPILER ERROR (compiler file ... Maybe the release mode tried to inline the destructor and goofed it ...
    (microsoft.public.vc.language)
  • Re: Internal compiler error problem
    ... INTERNAL COMPILER ERROR (compiler file ... helper class defined in the file and then i added some ... Maybe the release mode tried to inline the destructor and goofed it ...
    (microsoft.public.vc.language)
  • Re: Internal compiler error problem
    ... INTERNAL COMPILER ERROR (compiler file ... helper class defined in the file and then i added ... Maybe the release mode tried to inline the destructor and goofed it ...
    (microsoft.public.vc.language)
  • Re: C2783 in VS 6.0 but not in VS.NET 2003
    ... (compiler file 'msc1.cpp', line 2701) ... But I would personally prefer making GetPtr a member function. ...
    (microsoft.public.vc.language)
  • Re: Commented codes still affect the program
    ... I have "clean" on the main menu, but it will not do any good. ... Does it produce this effect regardless of which source file you have changed? ... I don't have VS 2003 installed and haven't used it for years but I remember one service pack added the command to clean the project getting rid of those files and fixing the problem which seems to have the source and the execution not in sync. ... If it was not on then the compiler could be out of sync. ...
    (microsoft.public.dotnet.framework.aspnet)