[Wine]interpreting debug messages

[Georg Fritsch]

Hi there

I'm in need of general information on

-          how to interpret debug information

-          how to tackle this systematically to improve my wine 
configuration



A certain, very special application I presently try to convince to run under 
wine, gives me the following messages:

wine: Unhandled exception (thread 0014), starting debugger...

WineDbg starting on pid 13

No debug information in ELF 'wine' ((nil))

Breakpoint 1 at 0x4000dd60

No debug information in ELF '/usr/lib/libntdll.dll.so' (0x40026000)

---following a whole bunch of similar *.so messages

No debug information in 32bit DLL 'C:\capi\projects\511140\511140.EXE' 
(0x400000)

---following further '32bit DLL' messages

Unhandled exception: page fault on write access to 0x00000004 in 32-bit code 
(0x5f856f43).

In 32-bit mode.

0x5f856f43 (MFC40.DLL.5421+0x14 in MFC40.DLL): movl 
%eax,0x4(%edx,%esi,1)

Wine-dbg>



Since I've no intention to dive into developing, I'm presently looking for a 
possible solution on the configuration level.

Can anybody tell me what to look for to resolve this or is there any other 
useful documentation besides the wine guides?



Any hints appreciated

Georg