This is the mail archive of the
cygwin-xfree
mailing list for the Cygwin XFree86 project.
Re: XWin.exe crashes on Windows restart
- From: Jon TURNEY <jon dot turney at dronecode dot org dot uk>
- To: cygwin-xfree at cygwin dot com
- Cc: andreasg123 at gmail dot com
- Date: Wed, 11 Sep 2013 17:51:02 +0100
- Subject: Re: XWin.exe crashes on Windows restart
- Authentication-results: sourceware.org; auth=none
- References: <CALt997=xeZUUduEbm6okoNFhTAF_LRETnHH+n1prjeOFq=pmSA at mail dot gmail dot com>
- Reply-to: cygwin-xfree at cygwin dot com
- Reply-to: cygwin-xfree <cygwin-xfree at cygwin dot com>
On 10/09/2013 22:16, Andreas Girgensohn wrote:
> I start XWin.exe via a shortcut when logging into Windows 7 (64-bit).
> Recently, I replaced my Cygwin installation with the 64-bit version.
> Now, XWin.exe crashes (SIGSEGV) every time I restart or shutdown
> Windows.
>
> I produced a gdb backtrace by cancelling the restart quickly after the
> problem occurred. Additional files are attached.
>
> (gdb) bt full
> #0 0x00000001004071ea in winMsgWindowProc (hwnd=<optimized out>,
> message=<optimized out>,
> wParam=<optimized out>, lParam=<optimized out>)
> at /usr/src/debug/xorg-server-1.14.2-2/hw/xwin/winmsgwindow.c:58
> pScreen = <optimized out>
> hwnd = <optimized out>
> message = 22
> wParam = <optimized out>
> lParam = <optimized out>
> #1 0x0000000077139bd1 in USER32!TranslateMessageEx ()
> from /cygdrive/c/Windows/system32/USER32.dll
> No symbol table info available.
> #2 0x000000000000050c in ?? ()
> No symbol table info available.
> #3 0x0000000000000001 in ?? ()
> No symbol table info available.
> #4 0x0000000000000000 in ?? ()
> No symbol table info available.
Thanks for reporting this problem, and providing the backtrace.
I've added a patch which should fix this crash and uploaded a snapshot at [1].
Perhaps you could try that and see if it improves things for you?
[1] ftp://cygwin.com/pub/cygwinx/XWin.x86_64.20130911-git-0919b42581c05bf8.exe.bz2
> On a different note, when running gdb, I noticed that XWin.exe twice
> receives a SIGSYS when starting. That does not affect normal
> operations.
This is expected when cygserver (which provides SySV shared memory) is not
running, as the X server tests to see if shared memory is available before
using it, by checking if shmget() causes a SIGSYS...
--
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/