[Wine] Debugging an application crash

James E. Lang jelly at ktb.net
Sun Feb 12 19:35:18 CST 2006

When a Windows application crashes (a rare occurrence) I see a set of messages 
like these:

wine: Unhandled page fault on read access to 0x429a3276 at address 0x4ba093 
(thread 0009), starting debugger...
err:seh:start_debugger Couldn't start debugger ("debugger/winedbg 8 9744") (2)
Read the Wine Developers Guide on how to set up winedbg or another debugger

I have not been able to figure out how to set up winedbg and I know nothing of 
any other debugger. Can someone spell this out for a simple minded user of 
Wine? By that I mean someone who does not begin to understand Wine's internal 

The whole debugging structure of Wine is a mystery to me. I have tried reading 
the Wine Developers Guide but I'm not a Wine Developer and what appears in that 
document goes right over my head. Some of us are simply people who want to be 
able to run a third party application that is intended for a Windows OS but we 
don't want the instability and vulnerability that goes with the M$ products. So 
. . . we use Linux and try to use Wine to support the Windows application.


More information about the wine-users mailing list