On Mon, 05 Nov 2001 12:08:40 +0900, "Stephen J. Turnbull"
<stephen(a)xemacs.org> said:
Lisp backtrace follows:
# bind (frame-being-created)
make-frame(nil #<x-device on ":0.0" 0x1bbe>)
frame-initialize()
# bind (debugger debug-on-error command-line-args-left)
command-line()
# (unwind-protect ...)
normal-top-level()
# (condition-case ... . error)
# (catch top-level ...)
(gdb) bt
#0 0x40227388 in XtInitializeWidgetClass () from /usr/X11R6/lib/libXt.so.6
#1 0x402276bb in XtInitializeWidgetClass () from /usr/X11R6/lib/libXt.so.6
#2 0x40227876 in XtInitializeWidgetClass () from /usr/X11R6/lib/libXt.so.6
#3 0x40228154 in _XtCreatePopupShell () from /usr/X11R6/lib/libXt.so.6
#4 0x402281e5 in XtCreatePopupShell () from /usr/X11R6/lib/libXt.so.6
#5 0x081700f8 in x_create_widgets (f=3D0x8469480, lisp_window_id=3D1363249=
64, parent=3D136324964)
at frame-x.c:1957
#6 0x08170704 in x_init_frame_1 (f=3D0x8469480, props=3D136324964) at fram=
e-x.c:2184
#7 0x080f874d in Fmake_frame (props=3D136324964, device=3D138290840) at fr=
ame.c:395
Am seeing this as well, after updating to the latest (20011214) RedHat Rawhide.
I am *suspecting*, but cannot prove, that the binutils-2.11.92.0.12-3 RPM
is at fault, mostly because over on the Enlightenment list, 2.11.92 gave
some Debian users pain as well. 2.11.90 seems to be OK based on word from
that list.
Also, compiling with --pdump works for me as well - probably because this
way it avoids the unexec() that seems to be giving binutils indigestion.
One for the PROBLEMS file?