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: jjreisert@alum.mit.edu Subject: Re: Dfficulty with xorg-server-1.17.1-2. Date: Wed, 25 Feb 2015 17:22:00 -0000 [thread overview] Message-ID: <54EDCD8F.7040608@dronecode.org.uk> (raw) In-Reply-To: <CAK-n8j7=OdZMX=uvZ3wEjufD7Xjgz1BZF1+pa0YYrCA+tjS4Fg@mail.gmail.com> On 25/02/2015 04:35, Jim Reisert AD1C wrote: > # gdb --pid=`pidof /usr/bin/XWin` > ... > Reading symbols from /usr/bin/XWin.exe...Reading symbols from /cygdrive/c/Cygwin > /lib/debug//usr/bin/XWin.exe.dbg...Can't read data for section '.debug_frame' in > file '/cygdrive/c/Cygwin/lib/debug/usr/bin/XWin.exe.dbg' > (gdb) c > Continuing. > Cannot execute this command while the selected thread is running. > (gdb) > > At this point, I can not right-click on the 'X' icon to do anything. > Once I exit gdb, then I can. How can I get past this? Odd. Are you sure you are using the current, cygwin gdb? But let's step back a moment, since I don't think you have the same problem as the OP. > [ 164.799] winClipboardProc - winClipboardFlushWindowsMessageQueue > trapped WM_QUIT message, exiting main loop. Perhaps we need to be a little more specific about what we mean by 'crashing'. This log message probably means that the X server is just spontaneously deciding it should exit, rather than exiting due to a program error signal with the "A fatal error has occurred" dialog. Can you provide a full Xwin.0.log file, please? I am assuming that this problem started with xorg-server 1.17 and reverting to 1.16.3-1 fixes it? -- 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:[~2015-02-25 13:26 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-02-24 18:13 GEORGE BARRICK 2015-02-24 19:36 ` Jim Reisert AD1C 2015-02-24 21:39 ` Jon TURNEY 2015-02-24 21:50 ` Jon TURNEY 2015-02-25 1:36 ` GEORGE BARRICK 2015-02-25 17:23 ` GEORGE BARRICK [not found] ` <54F2077C.9080802@dronecode.org.uk> 2015-03-01 14:06 ` GEORGE BARRICK 2015-02-25 13:26 ` Jim Reisert AD1C 2015-02-25 14:30 ` Jim Reisert AD1C 2015-02-25 17:22 ` Jon TURNEY [this message] 2015-02-24 21:44 ` 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=54EDCD8F.7040608@dronecode.org.uk \ --to=jon.turney@dronecode.org.uk \ --cc=cygwin-xfree@cygwin.com \ --cc=jjreisert@alum.mit.edu \ /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).