Author: Jon Dart
Date: 20:25:33 05/01/00
Go up one level in this thread
You can turn on debug info generation in your optimized build (remember to do it both in the C++ and Linker options panels) then rebuild and run the optimized program under the debugger. This should at least give you a stack trace to the place where your null pointer is being hit. As other posters have said, it is pretty likely this is a programming error and it just happends to be masked in debug mode. That can happen. But you should also get the latest service pack for Visual C++ (available from Microsoft's web site). It fixes numerous bugs, including some in the optimizer. --Jon On May 01, 2000 at 22:08:31, Landon Rabern wrote: >My program runs fine if I compile without the /O2 switch, but when I do it gives >this error when I run it: The instruction "0x0040000a" referenced memory at >"0x00000000", the memory could not be "written". > >I am running Windows 2000, could it be a problem with this? I just switched >over to windows 2000 before I got MSVC++ 6.0, so I dont know if it works in 98. > >Thanks, > >Landon W. Rabern
This page took 0 seconds to execute
Last modified: Thu, 15 Apr 21 08:11:13 -0700
Current Computer Chess Club Forums at Talkchess. This site by Sean Mintz.