Starting point to debug an application error

Mikołaj Zalewski mikolaj at
Thu Jul 17 04:46:38 CDT 2008

>If someone has the time to look at it, I'd love a pointer on where / how 
>to start investigating this..
  You could try to do a WINEDEBUG=+message,+seh log. This will give you 
all the messages, and a search for seh: lines will give you the 
exceptions that are being thrown/handled. Often, this will give 
information what message caused a crash in Wine control code or what 
notify caused a crash in application code.

Mikołaj Zalewski

More information about the wine-devel mailing list