Home Dashboard Directory Help
Search

VS 2008 RTM C++ Incremental Linker Crashes Frequently by ScottJ1s


Status: 

Closed
 as Not Reproducible Help for as Not Reproducible


22
0
Sign in
to vote
Type: Bug
ID: 318326
Opened: 12/17/2007 4:01:14 PM
Access Restriction: Public
2
Workaround(s)
view
25
User(s) can reproduce this bug

Description

In Visual Studio 2008 RTM, the C++ incremental linker crashes frequently. For interactive IDE builds, the problem is moderately severe, as the build will proceed with other compilation tasks, and a rebuild will remedy the earlier crash. For automated builds, it's more of a problem.
Details
Sign in to post a comment.
Posted by Deuscide on 3/17/2012 at 6:49 PM
Still having this problem. It seems to involve, for me, only projects that have dialogs via resource.rc files (created through the IDE). Same stats as bellow, completely different project.
Posted by Stargazer5a on 10/26/2011 at 2:29 PM
Fails 100%, all the time every time on Win7 SP1
Posted by Deuscide on 8/17/2011 at 7:10 AM
I get this bug during building of specific solutions (VS2008, Windows 7, latest Automatic Updates). This particular solution has several DLLs and some support libraries...

------ Build started: Project: DeviceEnumerationTest, Configuration: Debug Win32 ------
Compiling...
EnumTest.cpp
Linking...
LINK : fatal error LNK1000: Internal error during IncrBuildImage
Version 9.00.21022.08
ExceptionCode            = C0000005
ExceptionFlags         = 00000000
ExceptionAddress         = 00E1FCF7 (00DA0000) "C:\Program Files (x86)\Microsoft Visual Studio 9.0\VC\bin\link.exe"
NumberParameters         = 00000002
ExceptionInformation[ 0] = 00000000
ExceptionInformation[ 1] = 008DD670
CONTEXT:
Eax    = 400B6C48 Esp    = 0037EBC4
Ebx    = 40008170 Ebp    = 0037EBEC
Ecx    = 008DD670 Esi    = 400B6AB4
Edx    = 0037EBDC Edi    = 00DAD6C0
Eip    = 00E1FCF7 EFlags = 00010246
SegCs = 00000023 SegDs = 0000002B
SegSs = 0000002B SegEs = 0000002B
SegFs = 00000053 SegGs = 0000002B
Dr0    = 00000000 Dr3    = 00000000
Dr1    = 00000000 Dr6    = 00000000
Dr2    = 00000000 Dr7    = 00000000
Posted by grimicus on 12/9/2009 at 11:12 AM
This post was first on Google so I figured I'd put where I found the answer here:
http://smartclientfactory.blogspot.com/2008/04/visual-c-2008-incremental-link-hotfix.html
points to:
http://support.microsoft.com/kb/948127

And this seems to fix this problem, at least for me.
Posted by Juan Baez on 8/8/2009 at 9:11 AM
Try disabling the manifest; this seems to work for me and my peers.
Posted by dsackinger on 6/24/2008 at 2:30 PM
I see this frequently - multiple times a day. I also am running Vista64.
Posted by simdoc on 3/10/2008 at 2:33 PM
You may have the same problem as reported in Feedback ID 311732 and 297826. You may want to watch the activity there.
Posted by Cook32 on 2/28/2008 at 12:42 AM
Same problem
Upgrade solutions from 2005 to 2008 (1 with C++ project and 1 with C# project and a C++)

really bored about that.

Where to send my dump rep ?
Posted by squeakyMD on 1/23/2008 at 1:54 AM
Sorry, forgot to add that I'm using Vista 64-bit edition. Yet another 'benefit' to upgrading my OS!
Posted by squeakyMD on 1/23/2008 at 1:52 AM
This bug makes building of multiple projects take much longer as the only way to avoid this error seems to be to rebuild them all each time. Not exactly an efficiency feature!
Posted by Daniel_Smith on 1/20/2008 at 12:31 PM
I also get this multiple times per day. Using Vista 32, with projects migrated from VS 2005. Very frustrating, although a rebuild all usually takes care of it for a while.
Posted by Microsoft on 1/15/2008 at 11:56 AM
We have fixed the issue reported from other channels with similar description of the problem. However, without a crash dump, we are not able to determine whether the problem you have seen is the same as the one that we have known from similar reports.

If it is impossible for you to generate a crash dump or to send us a link repro (the instructions on how to do both of which are in the previous reply), we will have to assume it the same problem and close this issue at our end.

Thank you!
Posted by mpietras on 1/8/2008 at 8:56 AM
FYI - I'm hitting this multiple times per day on new projects I created on VS2008 (as opposed to migrated). I get fatal error LNK1000: Internal error during IncrBuildImage. I'm on Vista64 doing C++.
Posted by Microsoft on 12/27/2007 at 11:44 AM
Hello,

We have got similar reports from other channels. However, based on your description, we can't determine exactly whether the problem you encountered is the same as what we have already known.

Could you please send us a crash dump, or even better, a linker repro case?

To get a crash dump, set linker option /errorreport:prompt, more detailed instructions on how to set it is at http://msdn2.microsoft.com/en-us/library/ms235602(VS.80).aspx. When the crash occurred, a small window will prompt asking you to select a just-in-time debugger from a list (usually Visual Studio 2008 would be one of them). Select VS 2008. When VS starts up, a dialog box will show up asking you pick between break or continue. Select break. Then click menu "Debug" -> "Save Dump as".

To generate a link repro, please follow the instructions on either of the two pages:

http://support.microsoft.com/kb/134650, or
http://blogs.msdn.com/mlacey/archive/2006/07/25/678452.aspx.

Thanks!
Posted by Microsoft on 12/27/2007 at 11:41 AM
Hello,

We have got similar reports from other channels. However, based on your description, we can't determine exactly whether the problem you encountered is the same as what we have already known.

Could you please send us a crash dump, or even better, a linker repro case?

To get a crash dump, set linker option /errorreport:prompt, more detailed instructions on how to set it is at http://msdn2.microsoft.com/en-us/library/ms235602(VS.80).aspx. When the crash occurred, a small window will prompt asking you to select a just-in-time debugger from a list (usually Visual Studio 2008 would be one of them). Select VS 2008. When VS starts up, a dialog box will show up asking you pick between break or continue. Select break. Then click menu "Debug" -> "Save Dump as".

To generate a link repro, please follow the instructions on either of the two pages:

http://support.microsoft.com/kb/134650, or
http://blogs.msdn.com/mlacey/archive/2006/07/25/678452.aspx.

Thanks!
Posted by lstucki on 12/20/2007 at 10:23 AM
FYI - the project we get this on was originally developed on VS 2003 then migrated to VS 2005 then VS 2008. Don't know if that makes any difference or not. The project has both C++ and C# DLL's. There are some circular dependencies between a number of different dll's. So far if we do TWO builds we generally get past this. The first build has multiple problems - but the second build seems to work OK [So FAR]
Posted by lstucki on 12/20/2007 at 10:18 AM
We get this all the time too - it looks like the test team wasn't using Vista very much...
Posted by Microsoft on 12/17/2007 at 10:00 PM
Thanks for your feedback. We are escalating this issue to the appropriate group within the Visual Studio Product Team for triage and resolution. These specialized experts will follow-up with your issue.

Thank you,
Visual Studio Product Team
Sign in to post a workaround.
Posted by Juan Baez on 8/8/2009 at 9:09 AM
Disable manifest.
Posted by squeakyMD on 1/23/2008 at 1:50 AM
Revert to VS 2005 !!!