Codejock Forums Homepage
Forum Home Forum Home > Codejock Products > Visual C++ MFC > Toolkit Pro
  New Posts New Posts RSS Feed - Help: compiler error
  FAQ FAQ  Forum Search   Events   Register Register  Login Login

Help: compiler error

 Post Reply Post Reply
Author
Message
Jimor Marlow View Drop Down
Groupie
Groupie
Avatar

Joined: 03 June 2007
Location: Russian Federation
Status: Offline
Points: 30
Post Options Post Options   Thanks (0) Thanks(0)   Quote Jimor Marlow Quote  Post ReplyReply Direct Link To This Post Topic: Help: compiler error
    Posted: 18 February 2008 at 4:12pm
Hi, any help will be appreciated :)

I've upgraded my PC, installed fresh WinXP SP2, Visual Studio .Net 2003, CodeJock Toolkit 11.2.2.
Toolkit compiled succefully. When i've trying to rebuild my projects I've met few errors:

fatal error C1001: INTERNAL COMPILER ERROR (compiler file 'f:\vs70builds\3077\vc\Compiler\Utc\src\P2\p2symtab.c', line 4533)

May be someone could help me? What's wrong?
Back to Top
Smucker View Drop Down
Senior Member
Senior Member
Avatar

Joined: 02 February 2008
Status: Offline
Points: 156
Post Options Post Options   Thanks (0) Thanks(0)   Quote Smucker Quote  Post ReplyReply Direct Link To This Post Posted: 19 February 2008 at 5:17pm
I'm using VS 2005 now, but I do remember some weird internal compiler errors in VS 2003 resulting from:

1) Invalid TEMP folder, or TEMP folder full.
2) Insufficient virtual memory.
3) Different precompiler settings. Do a full rebuild.

(3) is I think your problem, see here:

http://support.microsoft.com/kb/141443



Product: Xtreme Toolkit Pro version 13.2 (Unicode, static build)

Platform: Windows 200x/XP/Vista/Win7 (32/64 bit)

Language: Visual C++ 9.0 (Studio 2008)

Back to Top
Jimor Marlow View Drop Down
Groupie
Groupie
Avatar

Joined: 03 June 2007
Location: Russian Federation
Status: Offline
Points: 30
Post Options Post Options   Thanks (0) Thanks(0)   Quote Jimor Marlow Quote  Post ReplyReply Direct Link To This Post Posted: 01 March 2008 at 3:40pm
I'm afraid it's not the problem. I'v got a lot of memory and always do full rebuild for all projects.

Wasted more than week trying to find errors in my code.
Moved all my huge project dlls to VS2008. It helped a little - still got few internal compiler errors (but less then in VS2003).
Then rolled back to 11.2.0 - and all OK. No one compiler error.

Now I've got two things, good (I've moved to new VS, at last!) and sad (my projects and new CodeJock toolkit version are incompatible now). What should I do? I want to have fresh CodeJock Toolkit everytime. I've planed to continue our company subscribtion and waiting for new features from 12.x :(
Back to Top
Oleg View Drop Down
Senior Member
Senior Member


Joined: 21 May 2003
Location: United States
Status: Offline
Points: 11234
Post Options Post Options   Thanks (0) Thanks(0)   Quote Oleg Quote  Post ReplyReply Direct Link To This Post Posted: 02 March 2008 at 1:46pm
Hi,
 
If you don't use some parts in your project like SyntaxEdit, ReportControl or Calendar, add in stdafx.h before you include Toolkit
 
#define _XTP_EXCLUDE_CALENDAR
#define _XTP_EXCLUDE_SYNTAXEDIT
#define _XTP_EXCLUDE_REPORTCONTROL
and compiler will skip these headers - it will save some time and heap.
Oleg, Support Team
CODEJOCK SOFTWARE SOLUTIONS
Back to Top
Jimor Marlow View Drop Down
Groupie
Groupie
Avatar

Joined: 03 June 2007
Location: Russian Federation
Status: Offline
Points: 30
Post Options Post Options   Thanks (0) Thanks(0)   Quote Jimor Marlow Quote  Post ReplyReply Direct Link To This Post Posted: 05 May 2008 at 10:03am
It's me again.
Moved to 12.0.0 (from 11.2.0) and have meet the old problem: internal compiler error in the same my dll.

after define _XTP_EXCLUDE_SYNTAXEDIT all works fine. To say trully it's no so fun. What have been changed in 11.2.2 (and in later version) comapred to 11.2.0? Sintax Edit not so important feature for me at this moment, but it's bad sign, IMHO.
Back to Top
Smucker View Drop Down
Senior Member
Senior Member
Avatar

Joined: 02 February 2008
Status: Offline
Points: 156
Post Options Post Options   Thanks (0) Thanks(0)   Quote Smucker Quote  Post ReplyReply Direct Link To This Post Posted: 06 May 2008 at 3:09am
You're misplacing the blame.

The only one it is a bad sign for is Microsoft. It's their compiler crashing!

There is some combination of your code, Codejock's code, and/or your system configuration that finds a bug in Microsoft's compiler.

Back to Top
Jimor Marlow View Drop Down
Groupie
Groupie
Avatar

Joined: 03 June 2007
Location: Russian Federation
Status: Offline
Points: 30
Post Options Post Options   Thanks (0) Thanks(0)   Quote Jimor Marlow Quote  Post ReplyReply Direct Link To This Post Posted: 06 May 2008 at 3:54am
I'm afraid, it's bad especially for me.
I adised to my company to use CodeJock Toolkit with VS2008, all was fine untill CodeJock added some changes and now compiler doesn't work as I want. My project has no changes. If it woild my code problme - I'd fix it, reaarange or change something to fit msft compiler. Now I couldn't. I don't blame CodeJock, I just inform them about my problems and hope they could made something. If not - it would be my problem again, I've made wrong decision about them. Even if MSFT are guilty, I can change my code, I can change toolkit (it would be very hard now), but I couldn't see alternative for VS now, we used it from 1996, 1.5 version :(
Back to Top
Smucker View Drop Down
Senior Member
Senior Member
Avatar

Joined: 02 February 2008
Status: Offline
Points: 156
Post Options Post Options   Thanks (0) Thanks(0)   Quote Smucker Quote  Post ReplyReply Direct Link To This Post Posted: 06 May 2008 at 11:13am
I don't have an alternative for VS either. I'm just saying that the internal compiler error is a bug in Visual Studio, not in Codejock!

Have you submitted an incident report to Microsoft? THEY are the ones that might be able to figure out what is wrong, since they have the source code and can at least tell what the compiler is doing when it fails. Codejock doesn't have that, so anything they did would just be guessing.

If lots of customers were having the problem, Codejock would have to try do something about it (and might have enough to go on by comparing projects, compiler settings, and system configurations). But when it's one customer, it's too difficult to even guess what the issue might be.

Here are some suggestions from having to deal with similar weird things in the past (I've used MS compilers since 1993):

1) Be sure you have plenty of virtual memory and free disk space. Don't let Windows manage your virtual memory settings; simply allocate fixed area(s) with a total of 8-16 GB for your page/swap file.

2) If the problem is consistently happening when compiling certain modules, you may be hitting an undocumented/unknown compiler limit (which should generate a "too many symbols" or "expression too complex" message rather than a crash.)

3) Learn everything YOU can about the problem. Try changing compiler options, try command line compiles, limit the number of concurrent compile threads, turn off incremental compiling/linking, try compiling on a different computer, etc.

Product: Xtreme Toolkit Pro version 13.2 (Unicode, static build)

Platform: Windows 200x/XP/Vista/Win7 (32/64 bit)

Language: Visual C++ 9.0 (Studio 2008)

Back to Top
Jimor Marlow View Drop Down
Groupie
Groupie
Avatar

Joined: 03 June 2007
Location: Russian Federation
Status: Offline
Points: 30
Post Options Post Options   Thanks (0) Thanks(0)   Quote Jimor Marlow Quote  Post ReplyReply Direct Link To This Post Posted: 07 May 2008 at 3:24am
Did it all.
Back to Top
 Post Reply Post Reply
  Share Topic   

Forum Jump Forum Permissions View Drop Down

Forum Software by Web Wiz Forums® version 12.04
Copyright ©2001-2021 Web Wiz Ltd.

This page was generated in 0.063 seconds.