FIX: Visual C++ 2013 can't detect buffer overruns or emit C4789 warnings

Symptoms

According to the MSDN library, when you compile C or C++ source code by using the Visual C++ 2013 C/C++ compiler, Visual C++ 2013 should detect some buffer overrun scenarios (of course only those that can be detected at compile time) and emit warning C4789.

However, some buffer overruns aren't caught with all optimization settings by Visual C++ 2013, even if you have installed the Visual Studio 2013 Update 5. No warning C4789 is emitted where the older version Visual C++ 2010 has successfully emitted warning C4789.

Note After you install this hotfix, Visual C++ 2013 can detect buffer overruns and emit the warning C4789 for Release configuration builds (in case /Od isn't used).

Cause

This issue occurs because of a problem in the Visual Studio 2013 C/C++ compiler .

Resolution

Hotfix information

The following file is available for download from the Microsoft Download Center:
Download Download the hotfix package now.

For more information about how to download Microsoft support files, click the following article number to view the article in the Microsoft Knowledge Base:
119591 How to obtain Microsoft support files from online services
Microsoft scanned this file for viruses. Microsoft used the most current virus-detection software that was available on the date that the file was posted. The file is stored on security-enhanced servers that help prevent any unauthorized changes to the file.

Prerequisites

To apply this hotfix, you must have Visual Studio 2013 installed.

Registry information

To use the hotfix in this package, you don't have to make any changes to the registry.

Restart requirement

You don't have to restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix doesn't replace a previously released hotfix.

Workaround

To work around this issue, use the /Oi Compiler Switch or Code Analysis to detect more instances of buffer overruns at compile time.

Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
Propriedades

ID do Artigo: 3170268 - Última Revisão: 21/07/2016 - Revisão: 1

Comentários