19 Jan
2006
19 Jan
'06
7:13 p.m.
Continuing my debugging efforts, I decided to look some more at the strange symbols I got in the backtrace. Indeed, it seems like winedbg completely screws up the MFC42 symbols. For example, by disassembling from the load address of MFC42 I was able to identify the CString::FreeData() function at 0x5f402125, but winedbg tells me it's 0x5f445900. Is this a known problem? Regards, -- Christer Palm