Ignore the bug report for the time being. The
winClipboardFlushWindowsMessageQueue message seems to be a part of
normal shutdown. I must have stopped the server myself last night.
When the one at home crashes, I'll post the files.
--
Jim Reisert AD1C, , http://www.ad1c.us
--
Unsubscribe info:
I've created a separate thread for tracking this problem.
The attached files are from the computer at work. I have never seen
the problem here before, only at home (both running Windows 7 64-bit).
The computer at home has been showing this symptom since later
versions of the server (1.6.x).
[118
2015.02.25.09:27:05
Hey Jon and cygwin staff,
As you surmised, the difficulty was with xlaunch starting the
new xwin-1.17.2-1. The xlaunch-20150224-1 that you posted
yesterday works like a charm.
I have one small note for other folks who might like to run
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.ex