xemacs-19.15p4 segfault on new frame -- xlib problem?
I recently upgraded to debian from redhat, and an interesting new
problem has surfaced with xemacs. I use a scrpt with gnudoit to
create new frames frequently. now when I run this script xemacs
coredumps frequently, especially after it's been running for a while.
When I look at the back-trace, the last instructions are in Xt stuff.
Similarly I noticed a little hack I did of xcpustate to run without
the label started coredumping. I hacked that a little more and it
seems to be ok.
However, it seems that the xlibs that come with debian are more
sensitive to problems in the code and more likely to cause a
segfault (?).
The libs on my redhat system... well, geez. I don't know what they
were. I switched them so many times--part of the reason I reinstalled
was to get a clean system since I had mucked around so much with my
old setup.
One thing I'm noticing now is that I have a hodgepodge of R6.1 libs
and R6.0 libs... e.g., libXt is 6.0, libX11 is 6.1... odd.
I installed debian off the ftp site, which, iirc, means I should have
the latest "stable" packages.
I compiled xemacs-19.15p4 on my own. It is otherwise stable.
Thoughts??
--sf
(here is a snippet from the backtrace:)
#0 0x402669b9 in __kill ()
#1 0x806f4dd in fatal_error_signal (sig=11) at emacs.c:202
#2 0xbfffe54c in ?? ()
#3 0x400b84c0 in XtInitializeWidgetClass ()
#4 0x400b8c72 in _XtCreatePopupShell ()
#5 0x400b8caf in XtCreatePopupShell ()
#6 0x80fa550 in x_create_widgets (f=0x890b600, lisp_window_id=404799492,
parent=404799492) at frame-x.c:1697
#7 0x80fa8d9 in x_init_frame_1 (f=0x890b600, props=404799492)
at frame-x.c:1928
#8 0x809b440 in Fmake_frame (props=404799492, device=405350656) at frame.c:424
[...]
--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
debian-user-request@lists.debian.org .
Trouble? e-mail to templin@bucknell.edu .
Reply to: