http://bugs.winehq.org/show_bug.cgi?id=20401
--- Comment #2 from Robert Hancock hancockrwd@gmail.com 2009-10-18 12:46:17 --- I'll try and test with a newer version at some point, there's no RPMs available for F11 yet to readily do this..
Some further info: it works fine on another machine I tried it on, which uses NVIDIA graphics. I think it's somehow related to Radeon graphics (this is with WINEDEBUG=warn+all):
warn:gdi:GDI_GetObjPtr Invalid handle (nil) warn:wgl:X11DRV_wglGetProcAddress (wglMakeContextCurrentARB) - not found warn:wgl:X11DRV_wglGetProcAddress (wglGetCurrentReadDCARB) - not found warn:wgl:X11DRV_wglGetProcAddress (wglCreatePbufferARB) - not found warn:wgl:X11DRV_wglGetProcAddress (wglGetPbufferDCARB) - not found warn:wgl:X11DRV_wglGetProcAddress (wglReleasePbufferDCARB) - not found warn:wgl:X11DRV_wglGetProcAddress (wglDestroyPbufferARB) - not found warn:wgl:X11DRV_wglGetProcAddress (wglQueryPbufferARB) - not found Allocating 16 x 16 radeon RBO (pitch 16) wine: Unhandled page fault on read access to 0x00000054 at address 0x6dbc2667 (thread 0009), starting debugger...
strace seems to show that the thread that prints the message about allocating radeon RBO is the same thread that segfaults shortly afterwards.
Not sure how I can get a backtrace, since the winedbg which gets automatically started upon the crash, also crashes:
wine: Unhandled page fault on read access to 0x0000002a at address 0x68501f23 (thread 001b), starting debugger...
which causes an infinite loop of "winedbg has encountered a serious problem" dialog boxes..