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, cygwin-xfree <cygwin-xfree@cygwin.com> Cc: boxer@bytezeppelin.com Subject: Re: XWin 1.12.1.0 seg faults on startup? Date: Mon, 25 Jun 2012 13:35:00 -0000 [thread overview] Message-ID: <4FE86913.2010706@dronecode.org.uk> (raw) In-Reply-To: <4FE29762.6070003@bytezeppelin.com> On 21/06/2012 04:39, Nick Vasilatos wrote: > Well... the new server (i1.12.2.0) also seg faults at 0x0 on startup. Debugger > says ``No Stack''? The log file is attached. > [Inferior 1 (process 17136) exited with code 01] > (gdb) bt full > No stack. > (gdb) This says that the XWin process exited, so either gdb somehow failed to catch it when it segfaulted. Or did it not segfault at all? > On 6/17/2012 10:09 AM, Jon TURNEY wrote: >> On 09/06/2012 17:32, Nick Vasilatos wrote: >>> XWin doesn't want to start for me. This is a new install of Cygwin/new install >>> of Win7 on an AMD x64 system with an Nvidia gtx-570 GPU; I've reinstalled the >>> X components a couple of times; rebasedall a couple of times. The log (I >>> installed an XWin.exe w/symbols) says: >>> >>> [ 5306.810] winPositionWindowMultiWindow: (x, y) = (0, 0) >>> [ 5306.810] immediately return since hWnd is NULL >>> [ 5306.810] winMapWindowMultiWindow - pWin: 80062268 >>> [ 5306.810] winUpdateWindowsWindow >>> [ 5306.810] winReshape () >>> [ 5306.826] Segmentation fault at address 0x0 So, this looks like maybe it's failing while trying to create a window, so this might be a timing condition at startup. You might try creating an empty ~/.startxwinrc (so the default xterm is not started by startxwin) and see if that makes a difference? -- 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:[~2012-06-25 13:35 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-06-09 16:33 Nick Vasilatos 2012-06-17 14:09 ` Jon TURNEY 2012-06-21 3:40 ` Nick Vasilatos 2012-06-25 13:35 ` Jon TURNEY [this message] 2012-06-27 15:34 ` Nick Vasilatos 2012-06-28 14:05 ` 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=4FE86913.2010706@dronecode.org.uk \ --to=jon.turney@dronecode.org.uk \ --cc=boxer@bytezeppelin.com \ --cc=cygwin-xfree@cygwin.com \ /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).