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/

Reply via email to