Core dump in emacs 24.3 on CYGWIN

Core dump in emacs 24.3 on CYGWIN

[Doug Lewan]

All, for several months I've been getting core dumps from emacs 24.3 running under CYGWIN. I try to update CYGWIN every week, but occasionally a week must be skipped.

Today is the first day I've gotten any specific information about any of these core dumps. (Usually it's just Aborted                 (core dumped) emacs). Today I got the following, more informative error. Still, it doesn't help me much in fixing the problem. (And it may, of course, just be a consequence of a memory management problem elsewhere.)

[xcb] Extra reply data still left in queue
[xcb] This is most likely caused by a broken X extension library
[xcb] Aborting, sorry about that.
assertion "!xcb_xlib_extra_reply_data_left" failed: file "/usr/src/ports/libX11/libX11-1.6.2-1/src/libX11-1.6.2/src/xcb_io.c", line 576, function: _XReply

Can anyone else help? (Can this help anyone?)

Thanks.

,Douglas
Douglas Lewan
Shubert Ticketing
(201) 489-8600 ext 224

Of course, shells have one feature that no other language has: subshells.

RE: Core dump in emacs 24.3 on CYGWIN

[Drew Adams]

> Today I got the following, more informative error. Still, it doesn't
> help me much in fixing the problem. (And it may, of course, just be a
> consequence of a memory management problem elsewhere.)
> 
> [xcb] Extra reply data still left in queue
> [xcb] This is most likely caused by a broken X extension library
> [xcb] Aborting, sorry about that.
> assertion "!xcb_xlib_extra_reply_data_left" failed: file
> "/usr/src/ports/libX11/libX11-1.6.2-1/src/libX11-1.6.2/src/xcb_io.c", line
> 576, function: _XReply
> 
> Can anyone else help? (Can this help anyone?)

My suggestion is `M-x report-emacs-bug'.  Pretty much any Emacs
crash indicates an Emacs bug: it should not crash.

Re: Core dump in emacs 24.3 on CYGWIN

[Eli Zaretskii]

> Date: Thu, 27 Feb 2014 08:17:20 -0800 (PST)
> From: Drew Adams <drew.adams@oracle.com>
> 
> > Today I got the following, more informative error. Still, it doesn't
> > help me much in fixing the problem. (And it may, of course, just be a
> > consequence of a memory management problem elsewhere.)
> > 
> > [xcb] Extra reply data still left in queue
> > [xcb] This is most likely caused by a broken X extension library
> > [xcb] Aborting, sorry about that.
> > assertion "!xcb_xlib_extra_reply_data_left" failed: file
> > "/usr/src/ports/libX11/libX11-1.6.2-1/src/libX11-1.6.2/src/xcb_io.c", line
> > 576, function: _XReply
> > 
> > Can anyone else help? (Can this help anyone?)
> 
> My suggestion is `M-x report-emacs-bug'.  Pretty much any Emacs
> crash indicates an Emacs bug: it should not crash.

The assertion is in Xlib, so I doubt that this is Emacs's fault.
Especially since no other Cygwin user of Emacs reported anything even
close.