Hallo,
I am trying to debug some missfunction in a programm (avrstudio.exe)
that uses MFC. The missfunction are senseless top/left/width/height
values to CreateWindowExA and that CreateWindowExA is called from the
MFC library. As VC++ comes with PDB files and source for the MFC
library, I thought that windebg should read that pdb files and then
would give me a sensible stack backtrace at that invokation of
CreateWindowExA.
However doing so it looks like:
0x405cdf46 (CreateWindowExA+0x46 [win.c:1118])
1118 FIXME("BON:Setting up SysHeader32\n");
Wine-dbg>bt
Backtrace:
=>0 0x405cdf46 (CreateWindowExA+0x46(exStyle=0x0, className=0x5f4a5444,
windowName=0x0, style=0x40000042, x=0x5f403903, y=0x5f4d1b60, width=0xa10af35d,
height=0xa0b2e4a0, parent=0x341c, menu=0x9c70, instance=0x400000, data=0x0)
[win.c:1118]) (ebp=4083cde0)
1 0x5f407d8a (COccManager::SplitDialogTemplate+0x6(pTemplate=0x0,
ppOleDlgItems=0x5f4a5444) [occmgr.cpp:182]) (ebp=4083ce50)
2 0x5f409a6b (MFC42.DLL.2124+0x46) (ebp=4083ce8c)
3 0x5f456a10 (MFC42.DLL.2093+0x2d) (ebp=ffffffff)
*** Invalid address 0xffffffff (SHLWAPI.DLL..reloc+0x4048dfff)
I wonder why the stack levels 2 and 3 don't get resolved in Function
names and looking at the MFC source for occmgr.cpp I think winedbg
doesn't get things right...
So my questions:
- Does winedbg do right here?
- Can I set a breakpoint in winedbg to
COccManager::SplitDialogTemplate and then single step line by
line. And how do I set the Breakpoint?
- Can I display variables in MFC? How do I do that.
Bye
Uwe Bonnes [EMAIL PROTECTED]
Free Software: If you contribute nothing, expect nothing
--
