The following comments are owned by whoever posted them. WineHQ is not responsible for what they say.
RE: Random Crashing as of the March 27 Version Update
by Megas of Vecanti on Friday March 30th 2012, 0:01
I'd highly suggest going on the freenode.net #WINE IRC channel and asking about exactly what would need to be done for a backtrace with full information in this case. I would assume that turning debug output to maximum and having someone walk you through winedbg would be necessary. Your rebuilding WINE with extra debugging and/or profiling flags may also be needed. (By default, you see, winedbg backtrace output doesn't tell you specifically what libraries caused the crash, only areas of memory that were affected when the app went down. If you have a more informative backtrace to show to the maintainers, there's a greater chance of the issue being isolated and fixed.)