From: Paul Graham <pgraham@oasys-ds.com>
To: bug-gnu-emacs@gnu.org
Subject: bug#3296: crash in ediff
Date: Fri, 15 May 2009 12:15:48 -0400 [thread overview]
Message-ID: <4A0D9534.2020309@oasys-ds.com> (raw)
Every so often, about once a week, my emacs session crashes while
running ediff. I'm enclosing a stack trace. I will be running ediff
comparing two directories. The crash occurs when I'm in the buffer
which lists pairs of files from the two directories. I select the next
pair to examine, and at the point emacs crashes.
I'm running this version:
This is GNU Emacs 22.2.1 (i386-redhat-linux-gnu, GTK+ Version 2.12.9)
of 2008-05-23 on xenbuilder4.fedora.phx.redhat.com
I'm running Fedora 9, Linux kernel 2.6.27.12-78.2.8.fc9.i686, GNOME 2.22.3.
Paul
Locking assertion failure. Backtrace:
#0 /usr/lib/libxcb-xlib.so.0 [0x656767]
#1 /usr/lib/libxcb-xlib.so.0(xcb_xlib_lock+0x2e) [0x65690e]
#2 /usr/lib/libX11.so.6 [0x595109]
#3 /usr/lib/libX11.so.6(XFlush+0x29) [0x56db39]
#4 /usr/lib/libgdk-x11-2.0.so.0(gdk_display_flush+0xa0) [0x869384]
#5 /usr/lib/libgdk-x11-2.0.so.0 [0x86012c]
#6 /usr/lib/libgdk-x11-2.0.so.0(gdk_window_process_all_updates+0xf8)
[0x860244]
#7 emacs [0x80cc9f2]
#8 emacs [0x80ccaa7]
#9 emacs [0x80cd105]
#10 emacs [0x80cd173]
#11 /usr/lib/libX11.so.6(_XError+0x109) [0x58da49]
#12 /usr/lib/libX11.so.6 [0x595ac8]
#13 /usr/lib/libX11.so.6(_XEventsQueued+0x55) [0x596435]
#14 /usr/lib/libX11.so.6(_XFlush+0x42) [0x5964c2]
#15 /usr/lib/libX11.so.6(XFlush+0x31) [0x56db41]
#16 emacs [0x80da290]
#17 emacs [0x8061839]
#18 emacs [0x8061c33]
#19 emacs [0x80dcb7d]
Locking assertion failure. Backtrace:
#0 /usr/lib/libxcb-xlib.so.0 [0x656767]
#1 /usr/lib/libxcb-xlib.so.0(xcb_xlib_lock+0x2e) [0x65690e]
#2 /usr/lib/libX11.so.6 [0x595109]
#3 /usr/lib/libX11.so.6(XFlush+0x29) [0x56db39]
#4 /usr/lib/libgdk-x11-2.0.so.0(gdk_display_flush+0xa0) [0x869384]
#5 /usr/lib/libgdk-x11-2.0.so.0 [0x86012c]
#6 /usr/lib/libgdk-x11-2.0.so.0(gdk_window_process_all_updates+0xf8)
[0x860244]
#7 emacs [0x80cc9f2]
#8 emacs [0x80ccaa7]
#9 emacs [0x80cd105]
#10 emacs [0x80cd173]
#11 /usr/lib/libX11.so.6(_XError+0x109) [0x58da49]
#12 /usr/lib/libX11.so.6 [0x595ac8]
#13 /usr/lib/libX11.so.6(_XEventsQueued+0x55) [0x596435]
#14 /usr/lib/libX11.so.6(_XFlush+0x42) [0x5964c2]
#15 /usr/lib/libX11.so.6(XFlush+0x31) [0x56db41]
#16 /usr/lib/libgdk-x11-2.0.so.0(gdk_display_flush+0xa0) [0x869384]
#17 /usr/lib/libgdk-x11-2.0.so.0 [0x86012c]
#18 /usr/lib/libgdk-x11-2.0.so.0(gdk_window_process_all_updates+0xf8)
[0x860244]
#19 emacs [0x80cc9f2]
Locking assertion failure. Backtrace:
#0 /usr/lib/libxcb-xlib.so.0 [0x656767]
#1 /usr/lib/libxcb-xlib.so.0(xcb_xlib_lock+0x2e) [0x65690e]
#2 /usr/lib/libX11.so.6 [0x595109]
#3 /usr/lib/libX11.so.6(XFlush+0x29) [0x56db39]
#4 /usr/lib/libgdk-x11-2.0.so.0(gdk_display_flush+0xa0) [0x869384]
#5 /usr/lib/libgdk-x11-2.0.so.0 [0x86012c]
#6 /usr/lib/libgdk-x11-2.0.so.0(gdk_window_process_all_updates+0xf8)
[0x860244]
#7 emacs [0x80cc9f2]
#8 emacs [0x80ccaa7]
#9 emacs [0x80cd105]
#10 emacs [0x80cd173]
#11 /usr/lib/libX11.so.6(_XError+0x109) [0x58da49]
#12 /usr/lib/libX11.so.6 [0x595ac8]
#13 /usr/lib/libX11.so.6(_XEventsQueued+0x55) [0x596435]
#14 /usr/lib/libX11.so.6(_XFlush+0x42) [0x5964c2]
#15 /usr/lib/libX11.so.6(XFlush+0x31) [0x56db41]
#16 /usr/lib/libgdk-x11-2.0.so.0(gdk_display_flush+0xa0) [0x869384]
#17 /usr/lib/libgdk-x11-2.0.so.0 [0x86012c]
#18 /usr/lib/libgdk-x11-2.0.so.0(gdk_window_process_all_updates+0xf8)
[0x860244]
#19 emacs [0x80cc9f2]
X protocol error: BadFont (invalid Font parameter) on protocol request 55
[1]+ Exit 70 emacs (wd: ~/oasys/sb)
(wd now: ~/oasys/sb/src)
[<sb> src]$
next reply other threads:[~2009-05-15 16:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-15 16:15 Paul Graham [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-01-01 22:19 bug#3296: crash in ediff Chong Yidong
2011-03-10 6:50 ` Glenn Morris
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=4A0D9534.2020309@oasys-ds.com \
--to=pgraham@oasys-ds.com \
--cc=3296@emacsbugs.donarmstrong.com \
--cc=bug-gnu-emacs@gnu.org \
/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: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.