segfault Xserver...current version (1.10, not 1.8)

[Jon TURNEY]

On 06/08/2011 19:01, Linda Walsh wrote:
>> 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]

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

I cannot reproduce this problem running yast2 from SuSE 11.4 on x86.

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

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?

No.

As I said once already:

> Following the instructions at [2] to obtain an Xserver backtrace would also be of great help.

[2] http://x.cygwin.com/devel/backtrace.html

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