Linker doesn't rebuild when stack reserve changed - by VoiceOfExperience

Status : 

  Fixed<br /><br />
		This item has been fixed in the current or upcoming version of this product.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.

Sign in
to vote
ID 711698 Comments
Status Closed Workarounds
Type Bug Repros 0
Opened 12/5/2011 3:30:29 PM
Access Restriction Public


When the stack reserve or commit value in the Linker is changed, the new values are not correctly built into the executable.

This is a bug also present in VS2010.
Sign in to post a comment.
Posted by Microsoft on 12/7/2011 at 10:17 AM
We have fixed the problem and the fix will be included in our next major release.

The workaround is to do "rebuild" (which would invoke a full linking) or use "editbin.exe" to directly modify the stack values in binary.

Thanks for taking the time to file the bug report. Please let us know if you have any other questions regarding this.

YongKang Zhu
VC++ CodeGen and Tools
Posted by MS-Moderator10 [Feedback Moderator] on 12/6/2011 at 1:48 AM
Thanks for your quick response. We are rerouting 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.
Posted by VoiceOfExperience on 12/6/2011 at 12:39 AM
I have successfully uploaded a zip file containing the solution files using the procedure you gave.
Posted by MS-Moderator10 on 12/5/2011 at 6:39 PM

You can use the following workspace to upload the files:
Password: 58oVCW*+@Q02Q

Please zip the file and use "FeedbackID-711698" as prefix of the file name.

Thank you.
Posted by VoiceOfExperience on 12/5/2011 at 5:42 PM
I have tried to attach the project files, but every time I submit, I get the error message "The following files were not successfully attached." I have reported this as a Connect bug.

Is there a way I can provide these files to Microsoft?
Posted by MS-Moderator01 on 12/5/2011 at 3:42 PM
Thank you for your feedback, we are currently reviewing the issue you have submitted. If this issue is urgent, please contact support directly(