segfault Xserver...current version (1.10, not 1.8)
Mon Aug 8 12:15:00 GMT 2011
On 06/08/2011 19:01, Linda Walsh wrote:
>> 1.8.0-1 is not the current version, 1.10.3-1 is (See ).
> I'm running 188.8.131.52 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
> Fatal server error:
> [100813.992] Caught signal 11 (Segmentation fault). Server aborting
>>> 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-.*)'
I cannot reproduce this problem running yast2 from SuSE 11.4 on x86.
>> Following the instructions at  to obtain an Xserver backtrace would also
>> be of great help.
>>> Previous version didn't have a problem.
>> 'Previous' is not a number.
>>> xorg-server 1.8.0-1 OK
> 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.
Does this mean that the xorg-server version reported by cygcheck is incorrect
because you've installed the tar file by hand?
I just cannot understand how you could paste your cygcheck.out, but not
mention that important fact.
Also, don't do that, it's not supported.
> Regarding a stack traceback -- I dont' see where the Xserver has produced
> a corefile to run gdb on (???). Does it produce one?
As I said once already:
> Following the instructions at  to obtain an Xserver backtrace would also be of great help.
Volunteer Cygwin/X X Server maintainer
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
More information about the Cygwin-xfree