469,909 Members | 1,630 Online
Bytes | Developer Community
New Post

Home Posts Topics Members FAQ

Post your question to a community of 469,909 developers. It's quick & easy.

fatal error C1001: INTERNAL COMPILER ERROR (compiler file 'msc1.cpp', line 2701)

Hello

I'm using the latest version of Visual Studio 2003 version 7.1.3088, .net framework 1.1.4322 and I've some problem compiling a project, it give me the error

c:\build\main\.....\methodeInc.h(36) : fatal error C1001: INTERNAL COMPILER ERRO
(compiler file 'msc1.cpp', line 2701)
Please choose the Technical Support command on the Visual C++
Help menu, or open the Technical Support help file for more informatio

I was able to reproduce the behaviour with this very little example, hope it helps you to fix the compiler

class

int i
public
B(int f) : i(f) {}
}

typedef B TB

class TB; <-------- that's the line that cause the compiler erro

Best Regards

- mn
Nov 17 '05 #1
9 14943
Marco Nova <no*******@removethis.hotmail.com> wrote:
[...]
I was able to reproduce the behaviour with this very little example, hope it helps you to fix the compiler.

class B
{
int i;
public:
B(int f) : i(f) {};
};

typedef B TB;

class TB; <-------- that's the line that cause the compiler error
Interesting. I found that, for VC7.1, this
is enough:

class B;
typedef B TB;
class TB;

I have Whidbey installed here, so I don't
know whether that's already fixed.
Best Regards,

- mn


Schobi

--
Sp******@gmx.de is never read
I'm Schobi at suespammers dot org

"Sometimes compilers are so much more reasonable than people."
Scott Meyers
Nov 17 '05 #2
Hendrik Schober <Sp******@gmx.de> wrote:
[...]

I have Whidbey installed here [...]


Er, I don't have.

Schobi
--
Sp******@gmx.de is never read
I'm Schobi at suespammers dot org

"Sometimes compilers are so much more reasonable than people."
Scott Meyers
Nov 17 '05 #3
Hendrik Schober wrote:
Marco Nova <no*******@removethis.hotmail.com> wrote:
[...]
I was able to reproduce the behaviour with this very little example,
hope it helps you to fix the compiler.

class B
{
int i;
public:
B(int f) : i(f) {};
};

typedef B TB;

class TB; <-------- that's the line that cause the
compiler error


Interesting. I found that, for VC7.1, this
is enough:

class B;
typedef B TB;
class TB;


The code is, of course, illegal. One ramification of that is that fixing
the compiler to give a better error message is a low priority fix.

I can report, however, that this particular ICE has in fact been fixed in
Whidbey.

-cd
Nov 17 '05 #4
Can MS just release a Service Pace as they've done with VC6.0?

"Carl Daniel [VC++ MVP]" <cp*****************************@mvps.org.nospam >
写入消息新闻:OC**************@tk2msftngp13.phx.gbl ...

The code is, of course, illegal. One ramification of that is that fixing
the compiler to give a better error message is a low priority fix.

I can report, however, that this particular ICE has in fact been fixed in
Whidbey.

Nov 17 '05 #5
IceJug wrote:
Can MS just release a Service Pace as they've done with VC6.0?


(Note that there's no "just" about it. It takes several months to put
together and test a service pack for Visual Studio).

Service packs for Visual Studio are by definition nothing more than
collections of QFEs (or "HotFixes"). (This is different from Windows and IE
service packs which frequently add significant new functionality).

By definition then, in order for a fix to be included in a Service Pack, it
must first be included in a QFE. Fixes are released as QFEs only as the
result of customers calling Product Support and requesting a fix for a
particular bug.

So, if you want a service pack fix for this bug, call Product Support.
Again though, given that the ICE occurs when parsing illegal code, it's less
likely that a QFE will actually be made (priority is, understandably, given
to fixing bugs that result in code that doesn't execute correctly, or that
result in compiler errors on valid source code).

-cd
Nov 17 '05 #6
> result of customers calling Product Support and requesting a fix for a
particular bug.


That sounds pretty easy. What's the number?
Nov 17 '05 #7
"Rudy Ray Moore" <ru*******@hotmail.com> wrote in message
news:er**************@TK2MSFTNGP12.phx.gbl...
result of customers calling Product Support and requesting a fix for a
particular bug.


That sounds pretty easy. What's the number?


Click Technical Support on the help menu. In the U.S. I think the number is

(800) 936-5800

Be sure to mention you are calling about a bug, not requesting paid support.

Regards,
Will
Nov 17 '05 #8
Rudy Ray Moore <ru*******@hotmail.com> wrote:
result of customers calling Product Support and requesting a fix for a
particular bug.


That sounds pretty easy. What's the number?

This

http://support.microsoft.com/default...;OfferProPhone

I found about a dozen clicks from the
MS home page. I'm not sure, though,
that this is what Carl suggested.

Schobi

--
Sp******@gmx.de is never read
I'm Schobi at suespammers dot org

"Sometimes compilers are so much more reasonable than people."
Scott Meyers
Nov 17 '05 #9
Rudy Ray Moore wrote:
result of customers calling Product Support and requesting a fix for
a particular bug.


That sounds pretty easy. What's the number?


See http://support.microsoft.com

Note that support calls generally incur charges (they cost money), and that
those charges are normally waived if the call is exclusively related to a
bug in a Microsoft product.

-cd
Nov 17 '05 #10

This discussion thread is closed

Replies have been disabled for this discussion.

Similar topics

reply views Thread by JimmyS | last post: by
1 post views Thread by Ray Mitchell | last post: by
1 post views Thread by ishbuu | last post: by
1 post views Thread by Waqarahmed | last post: by
reply views Thread by Salome Sato | last post: by
By using this site, you agree to our Privacy Policy and Terms of Use.