Segmentation Fault at startup - No core file produced
XEMACS seems to be crashing at initialization. I am using SUSE Linux and
GDB from an RPM file
Any ideas will be greatfully accepted.
Bob Bailey,
rlbailey(a)computer.org
(gdb) backtrace
#0 0x402b4888 in XtInitializeWidgetClass () from
/usr/X11R6/lib/libXt.so.6
#1 0x402b4bdf in xtWidgetAlloc () from /usr/X11R6/lib/libXt.so.6
#2 0x402b4dc0 in xtCreate () from /usr/X11R6/lib/libXt.so.6
#3 0x402b571b in _XtCreatePopupShell () from /usr/X11R6/lib/libXt.so.6
#4 0x402b57bd in XtCreatePopupShell () from /usr/X11R6/lib/libXt.so.6
#5 0x0817adb0 in x_create_widgets (f=0x848fee0,
lisp_window_id=136386532,
parent=136386532) at frame-x.c:1957
#6 0x0817b38d in x_init_frame_1 (f=0x848fee0, props=136386532)
at frame-x.c:2184
#7 0x080fed7c in Fmake_frame (props=136386532, device=136685688)
at frame.c:395
#8 0x080b0f1c in Ffuncall (nargs=3, args=0xbfffed88) at eval.c:3528
#9 0x0808bf99 in execute_optimized_program (
program=0x848fdc8 "Æ \210Ç ?&È\fÉ \"¬\027Ê\r\013\"\022Ë\rÈ\tÌ
\"＠\"\211\020\026\020Í\r!\025Î\016\021!\210Ï\211\024\207",
stack_depth=5,
constants_data=0x82b2d70) at bytecode.c:746
#10 0x0808bc79 in funcall_compiled_function (fun=137260152, nargs=0,
args=0xbfffeecc) at bytecode.c:515
#11 0x080b10bf in Ffuncall (nargs=1, args=0xbfffeec8) at eval.c:3563
#12 0x0808bf99 in execute_optimized_program (
program=0x825a150 "\013A\035ÆÇ\032\031È\r!\025\bÉa«\004Ê
\210ËÌ!«\004Í \210\f«\017\016\035¬\013ÎÏÐ\f!ÑQ! \210Ò \210*Ó \210Ô
\210rÕÖ!q\210× \210ØÙ!\210\016!Úa«\005\016\" \210)Û Üa«\bÝ ¬\004Þ \210ß
\210Ù\026#Ý \004àÇ!)\207ewA\001",
---Type <return> to continue, or q <return> to quit---
stack_depth=4, constants_data=0x83397c0) at bytecode.c:746
#13 0x0808bc79 in funcall_compiled_function (fun=137534068, nargs=0,
args=0xbfffef74) at bytecode.c:515
#14 0x080b0832 in Feval (form=137594324) at eval.c:3388
#15 0x080adc93 in condition_case_3 (bodyform=137594324, var=136506476,
handlers=137594228) at eval.c:1651
#16 0x0808c85f in execute_rare_opcode (stack_ptr=0xbffff1e0,
program_ptr=0x8270749 "\210Ì\r!\025\016.«\016ÚÓá\016.â ã
$!\0267äå!\210\016&«\005äæ!\210Ü\026&ç
\210\016(«\005äè!\210Ü\026(\t«\bé\t＠\tA\"\210)\0168\003ê
\207&\bä\027!\b¡", opcode=Bcondition_case) at bytecode.c:1271
#17 0x0808be1b in execute_optimized_program (
program=0x82706b8 "\b«\005ÆÇ!\207È\020É
\211\034«\025\fG\rGW«\016Ê\r!Ê\f!k«\005Ë\f!\025)Ì\r!\025Í \210Î
\210\013®\aÏÐ!\002È\eÑ\016/\0160\"\022\013«\tÒÓÔ\n\"Õ\"\210\n¬\004Ö
\210×\n\0161\016+\0162\013%\210Ø
\210)\016,¬\022\016-«\016ÙÚÛ\0163!\016-\"ÜÈ#\210\016,¬\024\016+¬\006Ý\0164!\210Ý\0165!\210Ý\0166!\210Ü\031Þßà\217\210Ì\r!\025\016.«\016ÚÓá\016.â
ã $!\0267äå!\210\016&«\005äæ!\210Ü\026&ç
\210\016(«\005äè!\210Ü\026(\t«\bé"..., stack_depth=7,
constants_data=0x83395d0)
at bytecode.c:656
#18 0x0808bc79 in funcall_compiled_function (fun=137534012, nargs=0,
args=0xbffff284) at bytecode.c:515
#19 0x080b0832 in Feval (form=137554036) at eval.c:3388
#20 0x080b6b06 in condition_case_1 (handlers=136386628,
bfun=0x80aff00 <Feval>, barg=137554036, hfun=0x8094720 <cmd_error>,
---Type <return> to continue, or q <return> to quit---
harg=136386532) at eval.c:1651
#21 0x080947af in top_level_1 (dummy=136386532) at cmdloop.c:206
#22 0x080b69cc in internal_catch (tag=136462628, func=0x8094780
<top_level_1>,
arg=136386532, threw=0x0) at eval.c:1317
#23 0x08094072 in initial_command_loop (load_me=136386532) at
cmdloop.c:285
#24 0x080aaacd in xemacs_21_4_8_i586_pc_linux () at emacs.c:2353
#25 0x080ac7f9 in main () at emacs.c:2782
#26 0x4051d7ee in __libc_start_main () from /lib/libc.so.6
(gdb) help back
Print backtrace of all stack frames, or innermost COUNT frames.
With a negative argument, print outermost -COUNT frames.
Use of the 'full' qualifier also prints the values of the local
variables.
(gdb) q
The program is running. Exit anyway? (y or n) y
bob＠darkstar:~> xemacs
Fatal error (11).
Your files have been auto-saved.
Use `M-x recover-session' to recover them.
If you have access to the PROBLEMS file that came with your
version of XEmacs, please check to see if your crash is described
there, as there may be a workaround available.
Otherwise, please report this bug by running the send-pr
script included with XEmacs, or selecting `Send Bug Report'
from the help menu.
As a last resort send ordinary email to `crashes(a)xemacs.org'.
*MAKE SURE* to include the information in the command
M-x describe-installation.
If at all possible, *please* try to obtain a C stack backtrace;
it will help us immensely in determining what went wrong.
To do this, locate the core file that was produced as a result
of this crash (it's usually called `core' and is located in the
directory in which you started the editor, or maybe in your home
directory), and type
gdb /usr/local/bin/xemacs core
then type `where' when the debugger prompt comes up.
(If you don't have GDB on your system, you might have DBX,
or XDB, or SDB. A similar procedure should work for all of
these. Ask your system administrator if you need more help.)
Lisp backtrace follows:
# bind (frame-being-created)
make-frame(nil #<x-device on ":0.0" 0x1bc4>)
frame-initialize()
# bind (debugger debug-on-error command-line-args-left)
command-line()
# (condition-case ... . ((t (byte-code " Â" ... 1))))
# bind (error-data)
normal-top-level()
# (condition-case ... . error)
# (catch top-level ...)
Segmentation fault