FIX: BreakPoints not hit for long file name DLL/EXE

 Last reviewed: September 19, 1997
Article ID: Q146447
4.00 4.10 WINDOWS NT kbprg kbbuglist kbfixlist

The information in this article applies to:

  • The development environment included with: Microsoft Visual C++, 32-bit Edition, versions 4.0, 4.1

SYMPTOMS

When running in debug mode using a dynamically loaded dynamic link library (DLL) such as an OLE control with a long file name or an .exe file with a long file name, you may find that it doesn't break at set break points. You may be able to set break points both before starting and while it is running, but the debugger will not break on them.

When starting the debug session, you may see the following message from the Microsoft Developer Studio: 

   One or more breakpoints cannot be set and have been disabled.
   Execution will stop at the beginning of the program.
If you receive this message and then attempt to set a break point in your code, you will not be able to do so and the Developer Studio will beep. If this message does not appear, you will be able to set break points, but they will be ignored.

This does not occur in Windows 95

CAUSE

The name of the DLL has more than eight characters.

RESOLUTION

Use DLL names of 8 characters or less.

STATUS

Microsoft has confirmed this to be a bug in the Microsoft products listed at the beginning of this article. This problem was corrected in Microsoft Visual C++, 32-bit Edition, version 4.2.

Additional reference words: 4.00 4.10 vcbuglist400 vcfixlist420
KBCategory: kbprg kbbuglist kbfixlist
KBSubcategory: MfcOLE

Keywords : MfcOLE kbbuglist kbfixlist kbprg
Technology : kbMfc
Version : 4.00 4.10
Platform : NT WINDOWS
Solution Type : kbfix

THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: September 19, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.