Microsoft KB Archive/99953

{|
 * width="100%"|

WinDbg Message &quot;Breakpoint Not Instantiated&quot;

 * }

Q99953

-

The information in this article applies to:


 * Microsoft Win32 Software Development Kit (SDK), versions 3.1, 3.5, 3.51, 4.0

-

The WinDbg message &quot;Breakpoint Not Instantiated&quot; indicates that the debugger could not resolve an address. This can happen for several reasons:


 * A specified symbol does not exist. In this case, check for misspelling and check the state of the &quot;ignore case&quot; option if the symbol contains mixed case.
 * The symbol exists, but the EXE or DLL was built with the wrong debugging information, or none at all. Use the -Zi and -Od compiler options and use the -debug:full, -debugtype:cv, and -pdb:none linker options.
 * The symbol exists, but it is in a module that has not yet been loaded. If the symbol is in a DLL that is dynamically loaded the breakpoint was probably set before the DLL was loaded. The message is harmless, because WinDbg will instantiated the BP when the module is loaded.

Additional query words: 3.10 3.50 4.00 95

Keywords :

Issue type :

Technology :