FIX: You receive a "The memory could not be 'read'" error message and Visual C++ debugger fails on some long names (243599)


The information in this article applies to:

  • The Integrated Debugger, when used with:
    • Microsoft Visual C++, 32-bit Editions 6.0
This article was previously published under Q243599

SYMPTOMS

When stopping at a breakpoint or stepping over a line in the Visual C++ debugger, you may receive an error like one of the following:
The instruction at "0x52512627" referenced memory at "0x00000000". The memory could not be "read".
The instruction at "0x5251263e" referenced memory at "0x00000003". The memory could not be "read".

CAUSE

An internal buffer overflow occurs on some long undecorated symbol names of functions or variables. The name won't necessarily appear to be long in the C++ source code.

RESOLUTION

A supported fix for Visual C++ 6.0 that corrects this problem is now available from Microsoft, but it has not been fully regression tested and should be applied only to systems experiencing this specific problem.

To resolve this problem immediately, contact Microsoft Product Support Services to obtain the fix. For a complete list of Microsoft Product Support Services phone numbers and information on support costs, visit the following address on the World Wide Web:

http://support.microsoft.com/default.aspx?scid=fh;EN-US;CNTACTMS

The English version of this fix should have the following file attributes or later:
NameSizeDateTimeVersion#Platform
Eecxx.dll184,3785/25/19996:03 PM6.0.8245.0x86

Note If this product was already installed on your computer when you purchased it from the Original Equipment Manufacturer (OEM) and you need this fix, please call the Pay Per Incident number listed on the above Web site. If you contact Microsoft to obtain this fix, a fee may be charged. This fee is refundable if it is determined that you only require the fix you requested. However, this fee is nonrefundable if you request additional technical support, if your no-charge technical support period has expired, or if you are not eligible for standard no-charge technical support.

STATUS

Microsoft has confirmed that this is a bug in the Microsoft products that are listed in the "Applies to" section. This bug was corrected in the latest service pack for Visual Studio 6.0.

For more information about Visual Studio service packs, click the following article numbers to view the articles in the Microsoft Knowledge Base:

194022 INFO: Visual Studio 6.0 Service packs, What, Where, Why

194295 HOWTO: Tell That a Visual Studio service Pack Is Installed

To download the latest Visual Studio service pack, visit the following Microsoft Web site:

http://msdn.microsoft.com/vstudio/downloads/updates/

Modification Type:MajorLast Reviewed:4/7/2006
Keywords:kbQFE KBHotfixServer kbBug kbDebug kbfix kbVC600fix kbVS600sp4fix kbVS600sp5fix KB243599
©2004 Microsoft Corporation. All rights reserved.