Re: segfault Xserver...current version (1.8)

[Linda Walsh <cygwin@tlinx.org>]

Jon TURNEY wrote:
> On 05/08/2011 01:02, Linda Walsh wrote:
>> /var/log/XWin> more XWin.0.log
>> [ 58452.716] winInitMultiWindowWM - XOpenDisplay () returned and 
>> successfully op
>> ened the display.
>> [ 58452.716] winMultiWindowXMsgProc - XOpenDisplay () returned and 
>> successfully
>> opened the display.
>> [ 58452.732] winClipboardProc - XOpenDisplay () returned and 
>> successfully opened
>> the display.
>> [ 58458.145] Segmentation fault at address 0x0
>> [ 58458.145]
>> Fatal server error:
>> [ 58458.145] Caught signal 11 (Segmentation fault). Server aborting
>> [ 58458.145]
>> ~
>> ~
>> ----
>> I just upgraded to the new server last night... 
> Next time, please *attach* the *full* XWin.0.log
---
	That was the full log...it had been truncated -- perhaps by the failing
processes...A full log from a "non-crashed version" (i.e. I haven't run 
yast2), is here:

/var/log/XWin> more XWin.0.log
Welcome to the XWin X Server
Vendor: The Cygwin/X Project
Release: 1.10.3.0
OS: Windows 7 Service Pack 1 [Windows NT 6.1 build 7601] (WoW64)
Package: version 1.10.3-1 built 2011-07-19

XWin was started with the following command line:

/usr/bin/XWin -dpi 101 -multiwindow -clipboard -nowinkill -wm

ddxProcessArgument - Initializing default screens
winInitializeScreenDefaults - primary monitor w 2560 h 1600
winInitializeDefaultScreens - native DPI x 120 y 120
[   938.034] (II) xorg.conf is not supported
[   938.034] (II) See http://x.cygwin.com/docs/faq/cygwin-x-faq.html for 
more in
formation
[   938.034] LoadPreferences: Loading //Bliss/law/.XWinrc
[   938.049] LoadPreferences: Done parsing the configuration file...
[   938.190] winDetectSupportedEngines - DirectDraw installed, allowing 
ShadowDD
[   938.190] winDetectSupportedEngines - Windows NT, allowing PrimaryDD
[   938.190] winDetectSupportedEngines - DirectDraw4 installed, allowing 
ShadowD
DNL
[   938.221] winDetectSupportedEngines - Returning, supported engines 
0000001f
[   938.221] winSetEngine - Multi Window or Rootless => ShadowGDI
[   938.221] winScreenInit - Using Windows display depth of 32 bits per 
pixel
[   938.221] winAllocateFBShadowGDI - Creating DIB with width: 4480 
height: 1600
  depth: 32
[   938.221] winFinishScreenInitFB - Masks: 00ff0000 0000ff00 000000ff
[   938.221] winInitVisualsShadowGDI - Masks 00ff0000 0000ff00 000000ff 
BPRGB 8
d 24 bpp 32
[   938.221] winInitMultiWindowWM - Calling pthread_mutex_lock ()
[   938.221] winMultiWindowXMsgProc - Calling pthread_mutex_lock ()
[   938.221] Screen 0 added at virtual desktop coordinate (0,0).
[   938.283] (II) AIGLX: Loaded and initialized /usr/lib/dri/swrast_dri.so
[   938.283] (II) GLX: Initialized DRISWRAST GL provider for screen 0
[   938.642] winPointerWarpCursor - Discarding first warp: 2240 800
[   938.642] (--) 7 mouse buttons found
[   938.642] (--) Setting autorepeat to delay=250, rate=31
[   938.642] (--) Windows keyboard layout: "00000409" (00000409) "US", 
type 4
[   938.642] (--) Found matching XKB configuration "English (USA)"
[   938.642] (--) Model = "pc105" Layout = "us" Variant = "none" Options 
= "none
"
[   938.642] Rules = "base" Model = "pc105" Layout = "us" Variant = 
"none" Optio
ns = "none"
[   938.642] winBlockHandler - pthread_mutex_unlock()
[   938.642] winInitMultiWindowWM - pthread_mutex_lock () returned.
[   938.642] winInitMultiWindowWM - pthread_mutex_unlock () returned.
[   938.642] winMultiWindowXMsgProc - pthread_mutex_lock () returned.
[   938.642] winInitMultiWindowWM - DISPLAY=:0.0
[   938.642] winMultiWindowXMsgProc - pthread_mutex_unlock () returned.
[   938.642] winProcEstablishConnection - winInitClipboard returned.
[   938.642] winMultiWindowXMsgProc - DISPLAY=:0.0
[   938.642] winClipboardProc - DISPLAY=:0.0
[   938.642] winInitMultiWindowWM - XOpenDisplay () returned and 
successfully op
ened the display.
[   938.658] winMultiWindowXMsgProc - XOpenDisplay () returned and 
successfully
opened the display.
[   938.673] winClipboardProc - XOpenDisplay () returned and 
successfully opened
  the display.
[  4096.679] OS has icon alpha channel support: yes

---------------------------

> 1.8.0-1 is not the current version, 1.10.3-1 is (See [1]).

I'm running 1.10.3.1 as you can see from the full log...

I will now crash my xserver...

[duplicate portions of above log suppressed...exactly the same timestamps
up to [4096.679]].
[100813.992] Segmentation fault at address 0x0
[100813.992]
Fatal server error:
[100813.992] Caught signal 11 (Segmentation fault). Server aborting
[100813.992]
---

I've no idea why the original log was truncated 'funny', other than I'd
tried to start and had crashed the server several times in a row,
so it's possible in the multiple invocations one log overwrote another.





> 
>> Works fine for most things...
>>
>> But ran yast2, on my suse box.... kills it every time. w/signal 11.
> 
> If this is still reproducible when you've upgraded to the current 
> version of the Xserver, can you tell me what SuSE version you are using, 
> please?
----
Suse 11.4
Ishtar:> rpm -qa|grep  -P '(?:patterns.*yast2)|(?:yast2.*ui-.*)'
yast2-ycp-ui-bindings-2.20.3-3.1.x86_64
patterns-openSUSE-yast2_install_wf-11.4-6.9.1.x86_64
yast2-ycp-ui-bindings-devel-2.20.3-3.1.x86_64
yast2-libyui-devel-2.20.2-3.1.x86_64
patterns-openSUSE-yast2_basis-11.4-6.9.1.x86_64
yast2-libyui-2.20.2-3.1.x86_64
---
xorg lib packages seem to be:
xorg-x11-libfontenc-7.6-6.1.x86_64
xorg-x11-libICE-7.6-8.1.x86_64
xorg-x11-libs-7.6-16.1.x86_64
xorg-x11-libSM-7.6-7.1.x86_64
xorg-x11-libX11-7.6-10.2.x86_64
xorg-x11-libX11-ccache-7.6-2.3.x86_64
xorg-x11-libXau-7.6_1.0.6-6.1.x86_64
xorg-x11-libxcb-7.6_1.7-8.1.x86_64
xorg-x11-libXdmcp-7.6-7.1.x86_64
xorg-x11-libXext-7.6_1.2.0-2.1.x86_64
xorg-x11-libXfixes-7.6_4.0.5-6.1.x86_64
xorg-x11-libxkbfile-7.6-6.1.x86_64
xorg-x11-libXmu-7.6-7.1.x86_64
xorg-x11-libXp-7.6-2.1.x86_64
xorg-x11-libXpm-7.6-6.1.x86_64
xorg-x11-libXprintUtil-7.6-2.1.x86_64
xorg-x11-libXrender-7.6_0.9.6-6.1.x86_64
xorg-x11-libXt-7.6_1.0.9-4.1.x86_64
xorg-x11-libXv-7.6-6.1.x86_64


> 
> Following the instructions at [2] to obtain an Xserver backtrace would 
> also be of great help.
---
> 
>> Previous version didn't have a problem.
> 
> 'Previous' is not a number.
> 
>> cygcheck.out:
> [snip]
>> xorg-server 1.8.0-1 OK
> [snip]
-----
	Yeah -- that's why I don't like to include cygcheck.out's
They give out lots of info that isn't _entirely_ relevant.  It's not even an
accurate package listing if one has installed packages w/tar by hand.

	
Regarding a stack traceback --   I dont' see where the Xserver has produced
a corefile to run gdb on (???).  Does it produce one?



--
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/