winedbg symbols completely screwed
eric.pouech at wanadoo.fr
Thu Jan 19 14:18:34 CST 2006
Christer Palm wrote:
> 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?
yes, when you have several versions of MFC42.PDB like you seem to do (we
don't lookup up for the right one yet)
More information about the wine-devel