7:29 a.m.
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
7:46 a.m.
>>>> "Bob" == Bob Bailey
<rlbaileyjr(a)worldnet.att.net> writes:
Hi Bob,
please provide version and configuration information for the XEmacs
you're trying to build.
Sending us your Installation file would do.
XEmacs Reviewers:
Shouldn't we forward bugs and crashes ＠ xemacs.org ot xemacs-beta or
such such list which is being archived?
Adrian
Bob> XEMACS seems to be crashing at initialization. I am using SUSE Linux and
Bob> GDB from an RPM file
Bob> Any ideas will be greatfully accepted.
Bob> Bob Bailey,
Bob> rlbailey(a)computer.org
Bob> (gdb) backtrace
Bob> #0 0x402b4888 in XtInitializeWidgetClass () from
Bob> /usr/X11R6/lib/libXt.so.6
Bob> #1 0x402b4bdf in xtWidgetAlloc () from /usr/X11R6/lib/libXt.so.6
Bob> #2 0x402b4dc0 in xtCreate () from /usr/X11R6/lib/libXt.so.6
Bob> #3 0x402b571b in _XtCreatePopupShell () from /usr/X11R6/lib/libXt.so.6
Bob> #4 0x402b57bd in XtCreatePopupShell () from /usr/X11R6/lib/libXt.so.6
Bob> #5 0x0817adb0 in x_create_widgets (f=0x848fee0,
Bob> lisp_window_id=136386532,
Bob> parent=136386532) at frame-x.c:1957
Bob> #6 0x0817b38d in x_init_frame_1 (f=0x848fee0, props=136386532)
Bob> at frame-x.c:2184
Bob> #7 0x080fed7c in Fmake_frame (props=136386532, device=136685688)
Bob> at frame.c:395
Bob> #8 0x080b0f1c in Ffuncall (nargs=3, args=0xbfffed88) at eval.c:3528
Bob> #9 0x0808bf99 in execute_optimized_program (
Bob> program=0x848fdc8 "Æ \210Ç ?&È\fÉ
\"¬\027Ê\r\013\"\022Ë\rÈ\tÌ
Bob> \"＠\"\211\020\026\020Í\r!\025Î\016\021!\210Ï\211\024\207",
Bob> stack_depth=5,
Bob> constants_data=0x82b2d70) at bytecode.c:746
Bob> #10 0x0808bc79 in funcall_compiled_function (fun=137260152, nargs=0,
Bob> args=0xbfffeecc) at bytecode.c:515
Bob> #11 0x080b10bf in Ffuncall (nargs=1, args=0xbfffeec8) at eval.c:3563
Bob> #12 0x0808bf99 in execute_optimized_program (
Bob> program=0x825a150 "\013A\035ÆÇ\032\031È\r!\025\bÉa«\004Ê
Bob> \210ËÌ!«\004Í \210\f«\017\016\035¬\013ÎÏÐ\f!ÑQ! \210Ò \210*Ó \210Ô
Bob> \210rÕÖ!q\210× \210ØÙ!\210\016!Úa«\005\016\" \210)Û Üa«\bÝ ¬\004Þ \210ß
Bob> \210Ù\026#Ý \004àÇ!)\207ewA\001",
Bob> ---Type <return> to continue, or q <return> to quit---
Bob> stack_depth=4, constants_data=0x83397c0) at bytecode.c:746
Bob> #13 0x0808bc79 in funcall_compiled_function (fun=137534068, nargs=0,
Bob> args=0xbfffef74) at bytecode.c:515
Bob> #14 0x080b0832 in Feval (form=137594324) at eval.c:3388
Bob> #15 0x080adc93 in condition_case_3 (bodyform=137594324, var=136506476,
Bob> handlers=137594228) at eval.c:1651
Bob> #16 0x0808c85f in execute_rare_opcode (stack_ptr=0xbffff1e0,
Bob> program_ptr=0x8270749 "\210Ì\r!\025\016.«\016ÚÓá\016.â ã
Bob> $!\0267äå!\210\016&«\005äæ!\210Ü\026&ç
Bob> \210\016(«\005äè!\210Ü\026(\t«\bé\t＠\tA\"\210)\0168\003ê
Bob> \207&\bä\027!\b¡", opcode=Bcondition_case) at bytecode.c:1271
Bob> #17 0x0808be1b in execute_optimized_program (
Bob> program=0x82706b8 "\b«\005ÆÇ!\207È\020É
Bob> \211\034«\025\fG\rGW«\016Ê\r!Ê\f!k«\005Ë\f!\025)Ì\r!\025Í \210Î
Bob>
\210\013®\aÏÐ!\002È\eÑ\016/\0160\"\022\013«\tÒÓÔ\n\"Õ\"\210\n¬\004Ö
Bob> \210×\n\0161\016+\0162\013%\210Ø
Bob>
\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.â
Bob> ã $!\0267äå!\210\016&«\005äæ!\210Ü\026&ç
Bob> \210\016(«\005äè!\210Ü\026(\t«\bé"..., stack_depth=7,
Bob> constants_data=0x83395d0)
Bob> at bytecode.c:656
Bob> #18 0x0808bc79 in funcall_compiled_function (fun=137534012, nargs=0,
Bob> args=0xbffff284) at bytecode.c:515
Bob> #19 0x080b0832 in Feval (form=137554036) at eval.c:3388
Bob> #20 0x080b6b06 in condition_case_1 (handlers=136386628,
Bob> bfun=0x80aff00 <Feval>, barg=137554036, hfun=0x8094720
<cmd_error>,
Bob> ---Type <return> to continue, or q <return> to quit---
Bob> harg=136386532) at eval.c:1651
Bob> #21 0x080947af in top_level_1 (dummy=136386532) at cmdloop.c:206
Bob> #22 0x080b69cc in internal_catch (tag=136462628, func=0x8094780
Bob> <top_level_1>,
Bob> arg=136386532, threw=0x0) at eval.c:1317
Bob> #23 0x08094072 in initial_command_loop (load_me=136386532) at
Bob> cmdloop.c:285
Bob> #24 0x080aaacd in xemacs_21_4_8_i586_pc_linux () at emacs.c:2353
Bob> #25 0x080ac7f9 in main () at emacs.c:2782
Bob> #26 0x4051d7ee in __libc_start_main () from /lib/libc.so.6
Bob> (gdb) help back
Bob> Print backtrace of all stack frames, or innermost COUNT frames.
Bob> With a negative argument, print outermost -COUNT frames.
Bob> Use of the 'full' qualifier also prints the values of the local
Bob> variables.
Bob> (gdb) q
Bob> The program is running. Exit anyway? (y or n) y
Bob> bob＠darkstar:~> xemacs
Bob> Fatal error (11).
Bob> Your files have been auto-saved.
Bob> Use `M-x recover-session' to recover them.
Bob> If you have access to the PROBLEMS file that came with your
Bob> version of XEmacs, please check to see if your crash is described
Bob> there, as there may be a workaround available.
Bob> Otherwise, please report this bug by running the send-pr
Bob> script included with XEmacs, or selecting `Send Bug Report'
Bob> from the help menu.
Bob> As a last resort send ordinary email to `crashes(a)xemacs.org'.
Bob> *MAKE SURE* to include the information in the command
Bob> M-x describe-installation.
Bob> If at all possible, *please* try to obtain a C stack backtrace;
Bob> it will help us immensely in determining what went wrong.
Bob> To do this, locate the core file that was produced as a result
Bob> of this crash (it's usually called `core' and is located in the
Bob> directory in which you started the editor, or maybe in your home
Bob> directory), and type
Bob> gdb /usr/local/bin/xemacs core
Bob> then type `where' when the debugger prompt comes up.
Bob> (If you don't have GDB on your system, you might have DBX,
Bob> or XDB, or SDB. A similar procedure should work for all of
Bob> these. Ask your system administrator if you need more help.)
Bob> Lisp backtrace follows:
Bob> # bind (frame-being-created)
Bob> make-frame(nil #<x-device on ":0.0" 0x1bc4>)
Bob> frame-initialize()
Bob> # bind (debugger debug-on-error command-line-args-left)
Bob> command-line()
Bob> # (condition-case ... . ((t (byte-code " Â" ... 1))))
Bob> # bind (error-data)
Bob> normal-top-level()
Bob> # (condition-case ... . error)
Bob> # (catch top-level ...)
Bob> Segmentation fault
--
Adrian Aichner
mailto:adrian＠xemacs.org
http://www.xemacs.org/
5:30 a.m.
Adrian,
I really should stop working late at night. At the time I made the
initial report, I was tired and lost track of what I was doing. I went
back to the original source code and started over. It has taken me
several days, but I now know what software I am working with.
At the time of the initial report, I was using xemacs 21.1.14 from an
RPM file I downloaded from the SUSE support site. I am now using Xemacs
21.1.14 built from sources. I had trouble rebuilding, console.elc would
not build. I copied console.el to console.elc, not expecting anything to
work but to my surprise, found I was now able to build.
I am still getting the segmenttion fault, without the core file. I have
reproduced the log from the invocation with GDB to the end of the dump.
I have attached the installation file.
Regards,
Bob
bob＠darkstar:~/xemacs/xemacs-21.1.14/src> gdb ./xemacs
GNU gdb 20010316
Copyright 2001 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you
are
welcome to change it and/or distribute copies of it under certain
conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty" for
details.
This GDB was configured as "i386-suse-linux"...
(gdb) g
Undefined command: "g". Try "help".
(gdb) r
Starting program: /home/bob/xemacs/xemacs-21.1.14/src/./xemacs
Program received signal SIGSEGV, Segmentation fault.
0x402b4888 in XtInitializeWidgetClass () from /usr/X11R6/lib/libXt.so.6
(gdb) h
List of classes of commands:
aliases -- Aliases of other commands
breakpoints -- Making program stop at certain points
data -- Examining data
files -- Specifying and examining files
internals -- Maintenance commands
obscure -- Obscure features
running -- Running the program
stack -- Examining the stack
status -- Status inquiries
support -- Support facilities
tracepoints -- Tracing of program execution without stopping the program
user-defined -- User-defined commands
Type "help" followed by a class name for a list of commands in that
class.
Type "help" followed by command name for full documentation.
Command name abbreviations are allowed if unambiguous.
(gdb) h stack
Examining the stack.
The stack is made up of stack frames. Gdb assigns numbers to stack
frames
counting from zero for the innermost (currently executing) frame.
At any time gdb identifies one frame as the "selected" frame.
Variable lookups are done with respect to the selected frame.
When the program being debugged stops, gdb selects the innermost frame.
The commands below can be used to select other frames by number or
address.
List of commands:
backtrace -- Print backtrace of all stack frames
bt -- Print backtrace of all stack frames
down -- Select and print stack frame called by this one
frame -- Select and print a stack frame
return -- Make selected stack frame return to its caller
select-frame -- Select a stack frame without printing anything
up -- Select and print stack frame that called this one
Type "help" followed by command name for full documentation.
Command name abbreviations are allowed if unambiguous.
(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 0x08150360 in x_create_widgets (f=0x83db610,
lisp_window_id=136930484,
parent=136930484) at frame-x.c:1952
#6 0x08150917 in x_init_frame_1 (f=0x83db610, props=136930484)
at frame-x.c:2183
#7 0x080ed941 in Fmake_frame (props=136930484, device=137796768)
at frame.c:383
#8 0x080a6aad in funcall_recording_as (recorded_as=137026732, nargs=2,
args=0xbfffe9d4) at eval.c:3197
#9 0x080aafb9 in Ffuncall (nargs=3, args=0xbfffe9d4) at eval.c:3238
#10 0x08086e89 in Fbyte_code (bytestr=136199808, vector=136199880,
maxdepth=11)
at bytecode.c:416
#11 0x080a77af in funcall_lambda (fun=136199968, nargs=0,
arg_vector=0xbfffecd8) at eval.c:3607
#12 0x080a6bb1 in funcall_recording_as (recorded_as=137332204, nargs=0,
args=0xbfffecd4) at eval.c:3214
#13 0x080aafb9 in Ffuncall (nargs=1, args=0xbfffecd4) at eval.c:3238
#14 0x08086e89 in Fbyte_code (bytestr=136335312, vector=136335428,
maxdepth=9)
at bytecode.c:416
---Type <return> to continue, or q <return> to quit---
#15 0x080a77af in funcall_lambda (fun=136335648, nargs=0,
arg_vector=0xbffff0d8) at eval.c:3607
#16 0x080a6bb1 in funcall_recording_as (recorded_as=137501020, nargs=0,
args=0xbffff0d4) at eval.c:3214
#17 0x080aafb9 in Ffuncall (nargs=1, args=0xbffff0d4) at eval.c:3238
#18 0x08086e89 in Fbyte_code (bytestr=136333184, vector=136333368,
maxdepth=13)
at bytecode.c:416
#19 0x080a77af in funcall_lambda (fun=136333888, nargs=0,
arg_vector=0xbffff1b4) at eval.c:3607
#20 0x080a735e in apply_lambda (fun=136333888, numargs=0,
unevalled_args=136930484) at eval.c:3511
#21 0x080a656f in Feval (form=137328260) at eval.c:3085
#22 0x080aac16 in condition_case_1 (handlers=136930596,
bfun=0x80a5c20 <Feval>, barg=137328260, hfun=0x808d960 <cmd_error>,
harg=136930484) at eval.c:1653
#23 0x0808d9ef in top_level_1 (dummy=136930484) at cmdloop.c:206
#24 0x080aaadc in internal_catch (tag=137004856, func=0x808d9c0
<top_level_1>,
arg=136930484, threw=0x0) at eval.c:1328
#25 0x0808d2b2 in initial_command_loop (load_me=136930484) at
cmdloop.c:285
#26 0x080a1ce8 in xemacs_21_1_14_i586_pc_linux () at emacs.c:1725
#27 0x080a3574 in main (argc=1, argv=0xbffff664, envp=0xbffff66c)
at emacs.c:2142
#28 0x4049d7ee in __libc_start_main () from /lib/libc.so.6
(gdb)
(gdb)
Adrian Aichner wrote:
>>>>> "Bob" == Bob Bailey <rlbaileyjr(a)worldnet.att.net>
writes:
Hi Bob,
please provide version and configuration information for the XEmacs
you're trying to build.
Sending us your Installation file would do.
XEmacs Reviewers:
Shouldn't we forward bugs and crashes ＠ xemacs.org ot xemacs-beta or
such such list which is being archived?
Adrian
Bob> XEMACS seems to be crashing at initialization. I am using SUSE Linux and
Bob> GDB from an RPM file
Bob> Any ideas will be greatfully accepted.
Bob> Bob Bailey,
Bob> rlbailey(a)computer.org
Bob> (gdb) backtrace
Bob> #0 0x402b4888 in XtInitializeWidgetClass () from
Bob> /usr/X11R6/lib/libXt.so.6
Bob> #1 0x402b4bdf in xtWidgetAlloc () from /usr/X11R6/lib/libXt.so.6
Bob> #2 0x402b4dc0 in xtCreate () from /usr/X11R6/lib/libXt.so.6
Bob> #3 0x402b571b in _XtCreatePopupShell () from /usr/X11R6/lib/libXt.so.6
Bob> #4 0x402b57bd in XtCreatePopupShell () from /usr/X11R6/lib/libXt.so.6
Bob> #5 0x0817adb0 in x_create_widgets (f=0x848fee0,
Bob> lisp_window_id=136386532,
Bob> parent=136386532) at frame-x.c:1957
Bob> #6 0x0817b38d in x_init_frame_1 (f=0x848fee0, props=136386532)
Bob> at frame-x.c:2184
Bob> #7 0x080fed7c in Fmake_frame (props=136386532, device=136685688)
Bob> at frame.c:395
Bob> #8 0x080b0f1c in Ffuncall (nargs=3, args=0xbfffed88) at eval.c:3528
Bob> #9 0x0808bf99 in execute_optimized_program (
Bob> program=0x848fdc8 "Æ \210Ç ?&È\fÉ
\"¬\027Ê\r\013\"\022Ë\rÈ\tÌ
Bob> \"＠\"\211\020\026\020Í\r!\025Î\016\021!\210Ï\211\024\207",
Bob> stack_depth=5,
Bob> constants_data=0x82b2d70) at bytecode.c:746
Bob> #10 0x0808bc79 in funcall_compiled_function (fun=137260152, nargs=0,
Bob> args=0xbfffeecc) at bytecode.c:515
Bob> #11 0x080b10bf in Ffuncall (nargs=1, args=0xbfffeec8) at eval.c:3563
Bob> #12 0x0808bf99 in execute_optimized_program (
Bob> program=0x825a150 "\013A\035ÆÇ\032\031È\r!\025\bÉa«\004Ê
Bob> \210ËÌ!«\004Í \210\f«\017\016\035¬\013ÎÏÐ\f!ÑQ! \210Ò \210*Ó \210Ô
Bob> \210rÕÖ!q\210× \210ØÙ!\210\016!Úa«\005\016\" \210)Û Üa«\bÝ ¬\004Þ \210ß
Bob> \210Ù\026#Ý \004àÇ!)\207ewA\001",
Bob> ---Type <return> to continue, or q <return> to quit---
Bob> stack_depth=4, constants_data=0x83397c0) at bytecode.c:746
Bob> #13 0x0808bc79 in funcall_compiled_function (fun=137534068, nargs=0,
Bob> args=0xbfffef74) at bytecode.c:515
Bob> #14 0x080b0832 in Feval (form=137594324) at eval.c:3388
Bob> #15 0x080adc93 in condition_case_3 (bodyform=137594324, var=136506476,
Bob> handlers=137594228) at eval.c:1651
Bob> #16 0x0808c85f in execute_rare_opcode (stack_ptr=0xbffff1e0,
Bob> program_ptr=0x8270749 "\210Ì\r!\025\016.«\016ÚÓá\016.â ã
Bob> $!\0267äå!\210\016&«\005äæ!\210Ü\026&ç
Bob> \210\016(«\005äè!\210Ü\026(\t«\bé\t＠\tA\"\210)\0168\003ê
Bob> \207&\bä\027!\b¡", opcode=Bcondition_case) at bytecode.c:1271
Bob> #17 0x0808be1b in execute_optimized_program (
Bob> program=0x82706b8 "\b«\005ÆÇ!\207È\020É
Bob> \211\034«\025\fG\rGW«\016Ê\r!Ê\f!k«\005Ë\f!\025)Ì\r!\025Í \210Î
Bob>
\210\013®\aÏÐ!\002È\eÑ\016/\0160\"\022\013«\tÒÓÔ\n\"Õ\"\210\n¬\004Ö
Bob> \210×\n\0161\016+\0162\013%\210Ø
Bob>
\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.â
Bob> ã $!\0267äå!\210\016&«\005äæ!\210Ü\026&ç
Bob> \210\016(«\005äè!\210Ü\026(\t«\bé"..., stack_depth=7,
Bob> constants_data=0x83395d0)
Bob> at bytecode.c:656
Bob> #18 0x0808bc79 in funcall_compiled_function (fun=137534012, nargs=0,
Bob> args=0xbffff284) at bytecode.c:515
Bob> #19 0x080b0832 in Feval (form=137554036) at eval.c:3388
Bob> #20 0x080b6b06 in condition_case_1 (handlers=136386628,
Bob> bfun=0x80aff00 <Feval>, barg=137554036, hfun=0x8094720
<cmd_error>,
Bob> ---Type <return> to continue, or q <return> to quit---
Bob> harg=136386532) at eval.c:1651
Bob> #21 0x080947af in top_level_1 (dummy=136386532) at cmdloop.c:206
Bob> #22 0x080b69cc in internal_catch (tag=136462628, func=0x8094780
Bob> <top_level_1>,
Bob> arg=136386532, threw=0x0) at eval.c:1317
Bob> #23 0x08094072 in initial_command_loop (load_me=136386532) at
Bob> cmdloop.c:285
Bob> #24 0x080aaacd in xemacs_21_4_8_i586_pc_linux () at emacs.c:2353
Bob> #25 0x080ac7f9 in main () at emacs.c:2782
Bob> #26 0x4051d7ee in __libc_start_main () from /lib/libc.so.6
Bob> (gdb) help back
Bob> Print backtrace of all stack frames, or innermost COUNT frames.
Bob> With a negative argument, print outermost -COUNT frames.
Bob> Use of the 'full' qualifier also prints the values of the local
Bob> variables.
Bob> (gdb) q
Bob> The program is running. Exit anyway? (y or n) y
Bob> bob＠darkstar:~> xemacs
Bob> Fatal error (11).
Bob> Your files have been auto-saved.
Bob> Use `M-x recover-session' to recover them.
Bob> If you have access to the PROBLEMS file that came with your
Bob> version of XEmacs, please check to see if your crash is described
Bob> there, as there may be a workaround available.
Bob> Otherwise, please report this bug by running the send-pr
Bob> script included with XEmacs, or selecting `Send Bug Report'
Bob> from the help menu.
Bob> As a last resort send ordinary email to `crashes(a)xemacs.org'.
Bob> *MAKE SURE* to include the information in the command
Bob> M-x describe-installation.
Bob> If at all possible, *please* try to obtain a C stack backtrace;
Bob> it will help us immensely in determining what went wrong.
Bob> To do this, locate the core file that was produced as a result
Bob> of this crash (it's usually called `core' and is located in the
Bob> directory in which you started the editor, or maybe in your home
Bob> directory), and type
Bob> gdb /usr/local/bin/xemacs core
Bob> then type `where' when the debugger prompt comes up.
Bob> (If you don't have GDB on your system, you might have DBX,
Bob> or XDB, or SDB. A similar procedure should work for all of
Bob> these. Ask your system administrator if you need more help.)
Bob> Lisp backtrace follows:
Bob> # bind (frame-being-created)
Bob> make-frame(nil #<x-device on ":0.0" 0x1bc4>)
Bob> frame-initialize()
Bob> # bind (debugger debug-on-error command-line-args-left)
Bob> command-line()
Bob> # (condition-case ... . ((t (byte-code " Â" ... 1))))
Bob> # bind (error-data)
Bob> normal-top-level()
Bob> # (condition-case ... . error)
Bob> # (catch top-level ...)
Bob> Segmentation fault
--
Adrian Aichner
mailto:adrian＠xemacs.org
http://www.xemacs.org/
uname -a: Linux darkstar 2.4.10-4GB #1 Fri Sep 28 17:20:21 GMT 2001 i586 unknown
./configure
XEmacs 21.1.14 "Cuyahoga Valley" configured for `i586-pc-linux'.
Where should the build process find the source code? /home/bob/xemacs/xemacs-21.1.14
What installation prefix should install use? /usr/local
What operating system and machine description files should XEmacs use?
`s/linux.h' and `m/intel386.h'
What compiler should XEmacs be built with? gcc -g -O3 -Wall -Wno-switch
Should XEmacs use the GNU version of malloc? yes
(Using Doug Lea's new malloc from the GNU C Library.)
Should XEmacs use the relocating allocator for buffers? yes
What window system should XEmacs use? x11
Where do we find X Windows header files? /usr/X11/include
Where do we find X Windows libraries? /usr/X11/lib
Compiling in support for XAUTH.
Compiling in support for XPM images.
Compiling in support for PNG image handling.
Compiling in support for (builtin) GIF image handling.
Compiling in support for JPEG image handling.
Compiling in support for TIFF image handling.
Compiling in native sound support.
Compiling in support for GNU DBM.
Compiling in support for ncurses.
Compiling in support for GPM (General Purpose Mouse).
Compiling in support for proper session-management.
Using Lucid menubars.
Using Lucid scrollbars.
Using Motif dialog boxes.
Compiling in DLL support.
movemail will use "dot-locking" for locking mail spool files.
Using Lisp_Objects with minimal tagbits.
8:54 a.m.
>>>> "Bob" == Bob Bailey
<rlbaileyjr(a)worldnet.att.net> writes:
Bob> Using Motif dialog boxes.
Try ./configure --with-dialogs=no.
This may be unusable for without dialogs, but if it works (ie, you get
a splash screen) we've fingered Motif as the culprit.
--
Institute of Policy and Planning Sciences http://turnbull.sk.tsukuba.ac.jp
University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN
My nostalgia for Icon makes me forget about any of the bad things. I don't
have much nostalgia for Perl, so its faults I remember. Scott Gilbert c.l.py
3:56 a.m.
Stephen,
It was the Hannibal Lecter version of ld.
Thanks for the help.
Bob
"Stephen J. Turnbull" wrote:
>>>>> "Bob" == Bob Bailey <rlbaileyjr(a)worldnet.att.net>
writes:
Bob> Using Motif dialog boxes.
Try ./configure --with-dialogs=no.
This may be unusable for without dialogs, but if it works (ie, you get
a splash screen) we've fingered Motif as the culprit.
--
Institute of Policy and Planning Sciences http://turnbull.sk.tsukuba.ac.jp
University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN
My nostalgia for Icon makes me forget about any of the bad things. I don't
have much nostalgia for Perl, so its faults I remember. Scott Gilbert c.l.py
7:17 a.m.
>>>> "Bob" == Bob Bailey
<rlbaileyjr(a)worldnet.att.net> writes:
Bob> XEMACS seems to be crashing at initialization. I am using
Bob> SUSE Linux and GDB from an RPM file
The crash signature suggests either
1. Hannibal Lecter ld. Use the --pdump argument to configure, or look
up "Hannibal Lecter" on the xemacs-beta list archives for
alternative ways to defeat the "feature" of ld.
2. OpenMotif/LessTif confusion. But it doesn't look like you have a
motif build (look for references to Motif in Installation).
--
Institute of Policy and Planning Sciences http://turnbull.sk.tsukuba.ac.jp
University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN
My nostalgia for Icon makes me forget about any of the bad things. I don't
have much nostalgia for Perl, so its faults I remember. Scott Gilbert c.l.py
8141
days inactive
8147
days old
5 comments
3 participants
participants (3)
-
Adrian Aichner -
Bob Bailey -
Stephen J. Turnbull