Community
cancel
Showing results for 
Search instead for 
Did you mean: 
kfsone
New Contributor I
117 Views

Build Cancel and Linker Crash

We have to recurring issues with the Intel C++ Compiler for Windows 7 which were present in 11.x and are still present now we have upgraded to 12. We're using VS9.
1- Build Cancel:
When you cancel a build, mpcom and icl.exe continue running. If you forget this or fail to notice, e.g. to correct a quick glaring typo infront of you, very strange things happen starting with an error regarding the PCH.
2- Linker Crash:
This happens to us about 1 time in 3 when building our main source project.
1>------ Rebuild All started: Project: WW2, Configuration: Debug Win32 ------
1>Compiling manifest to resources... (Microsoft VC++ Environment)
1>Microsoft Windows Resource Compiler Version 6.1.6723.1
1>
1>Copyright (C) Microsoft Corporation. All rights reserved.
1>
1>
1>Linking... (Intel C++ Environment)
1>ipo: warning #11073: tolua++.lib(tolua_map.obj): locally defined symbol __imp__strncat imported
1>xilink: executing 'link'
1>
1>LINK : fatal error LNK1000: Internal error during LinkerMain
1>
1> Version 9.00.30729.01
1>
1> ExceptionCode = C0000005
1> ExceptionFlags = 00000000
1> ExceptionAddress = 01328310
1> NumberParameters = 00000002
1> ExceptionInformation[ 0] = 00000008
1> ExceptionInformation[ 1] = 01328310
1>
1>CONTEXT:
1> Eax = 01328310 Esp = 003EEC5C
1> Ebx = 02A1B2CE Ebp = 003EEC74
1> Ecx = 3FFF03E8 Esi = 3FFF0410
1> Edx = 40D86428 Edi = 40D86420
1> Eip = 01328310 EFlags = 00010202
1> SegCs = 00000023 SegDs = 0000002B
1> SegSs = 0000002B SegEs = 0000002B
1> SegFs = 00000053 SegGs = 0000002B
1> Dr0 = 00000000 Dr3 = 00000000
1> Dr1 = 00000000 Dr6 = 00000000
1> Dr2 = 00000000 Dr7 = 00000000
1>
The work around is just to Build -> Project -> Build only {ProjectName} and linking completes happily.
0 Kudos
2 Replies
kfsone
New Contributor I
117 Views

Actually, happens to us on a number of different projects it seems.
JenniferJ
Moderator
117 Views

I've seen this and it's a VC bug. See http://support.microsoft.com/kb/948127. Installing VS2008 SP1 solves the issue.

Jennifer
Reply