Map file crash tracing
-
I have generated a MAP file for an MFC application with two threads. The load address in the MAP file is 0x00400000. But the program is showing a run-time error for an instruction at 0x77fcca41 which is refering to memory at 0xffffffff that could not be read. But there are no instruction at 0x77fcca41 in the MAP file. I would like to know whether anyone has come across such a problem and was able to trace the cause. If so some help is required
-
I have generated a MAP file for an MFC application with two threads. The load address in the MAP file is 0x00400000. But the program is showing a run-time error for an instruction at 0x77fcca41 which is refering to memory at 0xffffffff that could not be read. But there are no instruction at 0x77fcca41 in the MAP file. I would like to know whether anyone has come across such a problem and was able to trace the cause. If so some help is required
Debugging release builds using map files is outdated, unnecessary and inefficient. Simply enable debug information for your release build (be sure to do so for the compiler and linker) and debug as normal.
Steve
-
I have generated a MAP file for an MFC application with two threads. The load address in the MAP file is 0x00400000. But the program is showing a run-time error for an instruction at 0x77fcca41 which is refering to memory at 0xffffffff that could not be read. But there are no instruction at 0x77fcca41 in the MAP file. I would like to know whether anyone has come across such a problem and was able to trace the cause. If so some help is required
That address is in one of the OS DLLs. If you can repro the crash, run the EXE in the debugger and look at the stack trace when the crash happens. You can then look up the addresses that are on the stack.
--Mike-- Visual C++ MVP :cool: LINKS~! Ericahist | PimpFish | CP SearchBar v3.0 | C++ Forum FAQ Ford, what's this fish doing in my ear?