On 21/09/2010 23:06, Eliot Moss wrote:
Dear John -- Using the .bz2 you posted to this thread on Sept 7th or so, I consistently get SIGSEGV on my Windows-7 box whenever I Sleep or Hibernate the system. I include the .log file for your
Thanks for reporting this issue. Does the crash also occur if you don't use -resize?
consideration, and the stderr output. Earlier versions seemed to do ok. Is there a simple procedure for winding back?
If you've installed my snapshot as XWin.exe, the easiest way to get the 1.8.2-1 version back is to reinstall it using setup.
[snip]
[332511.061] winClipboardFlushXEvents - unexpected event type 34 [332532.557] winShadowUpdateDDNL - IDirectDrawSurface4_Blt () failed: 887601c2 [332533.556] winShadowUpdateDDNL - IDirectDrawSurface4_Blt () failed: 887601c2 [332534.554] winShadowUpdateDDNL - IDirectDrawSurface4_Blt () failed: 887601c2 [332535.553] winShadowUpdateDDNL - IDirectDrawSurface4_Blt () failed: 887601c2 [332536.551] winShadowUpdateDDNL - IDirectDrawSurface4_Blt () failed: 887601c2 [332537.550] winShadowUpdateDDNL - IDirectDrawSurface4_Blt () failed: 887601c2 [332538.564] winShadowUpdateDDNL - IDirectDrawSurface4_Blt () failed: 887601c2 [332539.578] winShadowUpdateDDNL - IDirectDrawSurface4_Blt () failed: 887601c2 [332547.237] winShadowUpdateDDNL - IDirectDrawSurface4_Blt () failed: 887601c2 [332549.343] winShadowUpdateDDNL - IDirectDrawSurface4_Blt () failed: 887601c2 [332549.343] winShadowUpdateDDNL - IDirectDrawSurface4_Blt failure message maximum (10) reached. No more failure messages will be printed. [332550.700] winWindowProc - WM_DISPLAYCHANGE - new bpp: 0 [332550.700] winWindowProc - WM_DISPLAYCHANGE - new width: 0 new height: 0 [332550.700] winCreatePrimarySurfaceShadowDDNL - Could not create primary surface: 8876024e [332550.700] Segmentation fault at address 0x0 [332550.700] Fatal server error: [332550.700] Caught signal 11 (Segmentation fault). Server aborting [332550.700]
Unfortunately, I can't reproduce this on my Win7 system, although it is quite possible that this is specific to the display driver or hardware.
If you can use gdb to generate a backtrace for this segfault, that would be most helpful.
-- Jon TURNEY Volunteer Cygwin/X X Server maintainer -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
