Re: XEmacs GUI hang when press n or p for a while in dired-mode

If you get a hang (which means infloop), at this point put a break on xcb_wait_for_event. Do 'continue' in gdb (you may need to do it twice to get XEmacs to run), and see if you get back to xcb_wait_for_event. If you do, then you need to single-step and see if control ever returns to XEmacs. My experience as reported in the bug above was that it does not; it infloops inside of Xt.

If so, that is an Xt bug. AFAICT, XEmacs never makes a blocking call to Xt without guarding it with XtAppPending, to make sure there is an event to process and therefore Xt will not block. > #3 0x00007f93ccc85688 in ?? () from /usr/lib/libX11.so.6 > #4 0x00007f93ccc85a3d in ?? () from /usr/lib/libX11.so.6 > #5 0x00007f93ccc862f9 in _XReadEvents () from /usr/lib/libX11.so.6 > #6 0x00007f93ccc64bd4 in XIfEvent () from /usr/lib/libX11.so.6 > #7 0x00007f93cccb0920 in ?? () from /usr/lib/libX11.so.6 > #8 0x00007f93cccafb69 in ?? () from /usr/lib/libX11.so.6 > #9 0x00007f93cccaff13 in _XimRead () from /usr/lib/libX11.so.6 > #10 0x00007f93ccc9ddf3 in ?? () from /usr/lib/libX11.so.6 > #11 0x00007f93ccc8b53a in XSetICValues () from /usr/lib/libX11.so.6 > #12 0x0000000000507f38 in XIM_SetSpotLocation (f=0x32c76f0, x=461, y=97) > at input-method-xlib.c:463 Are you actually using XIM?

If not, you can possibly get relief by using --with-xim=no, although I would prefer that you try to track down the bug (even though I believe it isn't ours, this is a nasty one!) N.B. ISTM I've seen XIM in backtraces where it has no business, ie, --with-xim=no builds. That suggests that Xlib or Xt is calling into XIM even though XEmacs doesn't want it.