Mikołaj Zalewski wrote: > >> 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.
Many many thanks. That took me about 50 seconds to pinpoint the problem! Now I just need to figure out what WINE does differently than Windows :) Regards, Brad
