http://bugs.winehq.org/show_bug.cgi?id=10213
--- Comment #21 from Thomas Stephenson admin@ubunto-tstephenson.com 2008-05-19 10:37:21 --- (In reply to comment #20)
(In reply to comment #18)
(In reply to comment #9)
Continues to happen with the current version. I'm a member of the Pegasus Mail beta team using the closed beta version v4.50 using the Visual C++ compiler rather than the Borland compiler. With windows we're able to use the WinDBG application to detect failures and report exactly what has failed. Is there a similar tool for Wine?
There is a debug tool in Wine, the following link gives an outline.
http://www.hscripts.com/tutorials/linux-services/wine.html
Geoff Lane
It would be helpful for a pointer to an example on how this actually works on a Linux workstation. I've tried running the program with winedbg rather than wine but I have no errors our any other output when the program goes away. It implies that there should be some sort of error logging someplace when there is an error, but it's not all that clear to me how this works.
FWIW, this is what I get when running with winedbg. This is not what I would normally see if I was using the WinDbg debugger. Obviously I do not really know how to use this tool.
root@ubuntu:~# winedbg /root/.wine/drive_c/pmail/programs/winpm-32.exe -a -ms WineDbg starting on pid 003c 0x7b876f52: movl %esi,0x0(%esp) Wine-dbg>step Single stepping until exit from function, which has no line number information. fixme:ntdll:NtLockFile I/O completion on lock not implemented yet fixme:storage:StgCreateDocfile Transacted mode not implemented. Invalid address (0x7b876f57) for breakpoint 0, disabling it Process of pid=003c has terminated