public inbox for cygwin-xfree@sourceware.org help / color / mirror / Atom feed
From: Jon TURNEY <jon.turney@dronecode.org.uk> To: cygwin-xfree@cygwin.com Cc: cygwin@tlinx.org Subject: Re: segfault Xserver...current version (1.10, not 1.8) Date: Mon, 08 Aug 2011 12:15:00 -0000 [thread overview] Message-ID: <4E3FD322.2040804@dronecode.org.uk> (raw) In-Reply-To: <4E3D8169.8050801@tlinx.org> 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/
next prev parent reply other threads:[~2011-08-08 12:15 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-08-05 0:04 segfault Xserver...current version (1.8) Linda Walsh 2011-08-06 15:57 ` Jon TURNEY 2011-08-06 18:01 ` Linda Walsh 2011-08-07 11:26 ` Csaba Raduly 2011-08-08 6:37 ` Linda Walsh 2011-08-08 12:15 ` Jon TURNEY [this message] 2011-08-08 23:40 ` segfault Xserver...current version (1.10, not 1.8) Linda Walsh 2011-08-10 14:41 ` Jon TURNEY 2011-08-10 0:55 ` Linda Walsh 2011-08-10 5:11 ` Christopher Faylor 2011-08-16 7:16 ` Linda Walsh 2011-08-16 12:28 ` Jon TURNEY
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=4E3FD322.2040804@dronecode.org.uk \ --to=jon.turney@dronecode.org.uk \ --cc=cygwin-xfree@cygwin.com \ --cc=cygwin@tlinx.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).