Christer Palm wrote:
Eric Pouech wrote:
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)
A+
The thing is that I can't see that this is the case here. I have:
[EMAIL PROTECTED] ~]$ find ~/.wine/drive_c/ -name "MFC*" -o -name "mfc*"
from one of your previous posts:
wine: Unhandled page fault on read access to 0x0000003c at address 0x5f4056dd
(thread 0009), starting debugger...
WineDbg starting on pid 0x8
Unhandled exception: page fault on read access to 0x0000003c in 32-bit code
(0x5f4056dd).
In 32 bit mode.
fixme:dbghelp:sffip_cb NIY on 'E:\8168\vc98\mfc\mfc.bbt\src\mfc42.pdb'
fixme:dbghelp:sffip_cb NIY on 'C:\hager\Semiolog\Apps\MFC42.PDB'
fixme:dbghelp_msc:codeview_parse_type_table Not adding parameters' types to
function signature
fixme:dbghelp_msc:codeview_parse_type_table Unsupported type-id leaf a
fixme:dbghelp_msc:dump 00000000: 06 00 0a 00 01 00 50 f1 ......P.
fixme:dbghelp_msc:codeview_get_type Returning NULL symt for type-id 1053
also, we don't check (yet) CRC when loading PDB, which may also be the
issue.
A+
--
Eric Pouech
