On Thu, 30 Oct 2003, Harold L Hunt II wrote:
> Frédéric L. W. Meunier wrote:
> > As soon as I start snes9x.exe 1.41-1 (a Super Nintendo emulator
> > - http://www.snes9x.com/) the server crashes with the
> > following:
> >
> > xinit: connection to X server lost.
> > XIO: fatal IO error 104 (Connection reset by peer) on X server ":0.0"
> > after 10719 requests (10623 known processed) with 0 events remaining.
> > XIO: fatal IO error 104 (Connection reset by peer) on X server ":0.0"
> > after 81713 requests (81698 known processed) with 0 events remaining.
> >
> > [1]+ Done startx
> >
> > Is this a bug ? Are any applications supposed to make XWin.exe
> > crash ?
>
> Not a known bug. No application should cause XWin.exe to crash.
>
> I tried this on my system (Win XP Pro SP1a + all latest patches) and
> could not reproduce the problem.
I also have Professional (I ommited it) and all latest patches.
> I tried it with both -multiwindow (uses GDI engine)
It didn't crash.
> and with -nodecoration -lesspointer (uses DirectDraw engine).
It crashed.
> Neither crashed when snes9x.exe was launched.
Before I was using -rootless -emulate3buttons -clipboard
> Try the above two tests as I did.
> Have you already loaded a ROM in snes9x.exe? Does it cache
> this and try to load it on the next startup? If so, perhaps
> that is causing the problem. I do not have any ROMs, so I
> cannot test that further.
You don't need any. With -nodecoration -lesspointer or
-rootless -emulate3buttons -clipboard it crashes as soon as I
close it. I thought it crashed when I started it. I assume I
was wrong.
> Try starting with startxwin.bat instead of startx. You could
> actually be seeing a crash in one of the sub-apps launched by
> xinit, which might be causing the server to be killed.
In fact, the error messages are different if I use IceWM or
twm. With twm it still crashes, but only displays:
xinit: connection to X server lost.
X connection to :0.0 broken (explicit kill or server shutdown).
> Please send in /tmp/XWin.log from one of these crashes as
> well.
Attached.
Does it mean something with resolution or color depth ? Under
Display Properties I see 1024x768x32bpp.
I ran the emulator with default settings.
--
How to contact me - http://www.pervalidus.net/contact.html
ddxProcessArgument - Initializing default screens
winInitializeDefaultScreens - w 1024 h 768
winInitializeDefaultScreens - Returning
OsVendorInit - Creating bogus screen 0
_XSERVTransmkdir: Owner of /tmp/.X11-unix should be set to root
(EE) Unable to locate/open config file
InitOutput - Error reading config file
winDetectSupportedEngines - Windows NT/2000/XP
winDetectSupportedEngines - DirectDraw installed
winDetectSupportedEngines - Allowing PrimaryDD
winDetectSupportedEngines - DirectDraw4 installed
winDetectSupportedEngines - Returning, supported engines 0000001f
InitOutput - g_iNumScreens: 1 iMaxConsecutiveScreen: 1
winSetEngine - Using Shadow DirectDraw NonLocking
winAdjustVideoModeShadowDDNL - Using Windows display depth of 32 bits per pixel
winCreateBoundingWindowWindowed - User w: 1024 h: 768
winCreateBoundingWindowWindowed - Current w: 1024 h: 768
winAdjustForAutoHide - Original WorkArea: 0 0 738 1024
winAdjustForAutoHide - Adjusted WorkArea: 0 0 738 1024
winCreateBoundingWindowWindowed - WindowClient w 1024 h 738 r 1024 l 0 b 738 t 0
winCreateBoundingWindowWindowed - Returning
winCreatePrimarySurfaceShadowDDNL - Creating primary surface
winCreatePrimarySurfaceShadowDDNL - Created primary surface
winCreatePrimarySurfaceShadowDDNL - Attached clipper to primary surface
winAllocateFBShadowDDNL - lPitch: 4096
winAllocateFBShadowDDNL - Created shadow pitch: 4096
winAllocateFBShadowDDNL - Created shadow stride: 1024
winFinishScreenInitFB - Masks: 00ff0000 0000ff00 000000ff
winInitVisualsShadowDDNL - Masks 00ff0000 0000ff00 000000ff BPRGB 8 d 24 bpp 32
winCreateDefColormap - Deferring to fbCreateDefColormap ()
winFinishScreenInitFB - returning
winScreenInit - returning
InitOutput - Returning.
MIT-SHM extension disabled due to lack of kernel support
XFree86-Bigfont extension local-client optimization disabled due to lack of shared
memory support in the kernel
(==) winConfigKeyboard - Layout: "00010416" (00010416)
(==) Using preset keyboard for "Portuguese (Brazil, ABNT2)" (10416), type "4"
(EE) No primary keyboard configured
(==) Using compiletime defaults for keyboard
Rules = "xfree86" Model = "abnt2" Layout = "br" Variant = "(null)" Options = "(null)"
Could not init font path element /usr/X11R6/lib/X11/fonts/Speedo/, removing from list!
Could not init font path element /usr/X11R6/lib/X11/fonts/CID/, removing from list!
winPointerWarpCursor - Discarding first warp: 512 369
winBlockHandler - Releasing pmServerStarted
winBlockHandler - pthread_mutex_unlock () returned
winWindowProc - WM_DISPLAYCHANGE - orig bpp: 32, last bpp: 32, new bpp: 16
winWindowProc - WM_DISPLAYCHANGE - new width: 640 new height: 480
winWindowProc - Disruptive change in depth
winDisplayDepthChangeDialog - DialogBox returned: 5440166
winDisplayDepthChangeDialog - GetLastError: 0
winReleasePrimarySurfaceShadowDDNL - Hello
winReleasePrimarySurfaceShadowDDNL - Detached clipper
winReleasePrimarySurfaceShadowDDNL - Released primary surface
winCreatePrimarySurfaceShadowDDNL - Creating primary surface
winCreatePrimarySurfaceShadowDDNL - Could not create primary surface: 887600e1
winChangeDelthDlgProc - wParam == s_pScreenInfo->dwBPP
winWindowProc - WM_ACTIVATE - Bad depth, trying to override window activation
winWindowProc - WM_DISPLAYCHANGE - orig bpp: 32, last bpp: 16, new bpp: 32
winWindowProc - WM_DISPLAYCHANGE - new width: 1024 new height: 768
winReleasePrimarySurfaceShadowDDNL - Hello
winReleasePrimarySurfaceShadowDDNL - Released primary surface
winCreatePrimarySurfaceShadowDDNL - Creating primary surface
winCreatePrimarySurfaceShadowDDNL - Could not create primary surface: 887600e1
