10:24 p.m.
FYI,
I just grabbed the latest 21.2 sources via CVS this morning, and
XEmacs core dumps at startup. When I start XEmacs, the X window
appears, and then xemacs immediately dumps core:
========================================================================
$ ./xemacs -q -vanilla
Fatal error (10).
Your files have been auto-saved.
Use `M-x recover-session' to recover them.
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 /users/darrylo/d0/gnu/outside-XEmacs/xemacs-21.2/src/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:
resize-subwindow(#<image-instance (widget) on #<x-device on
"mina.sr.hp.com:0.0" 0x19a0> (#<face default "default
face">)Buffers 1785x28 on #<x-frame > 0x403ad100 0x1dca> 1785 nil)
# bind (inst frame-or-buffer)
update-tab-in-gutter(#<buffer "*scratch*">)
# bind (frame-being-created)
make-frame(nil #<x-device on "mina.sr.hp.com:0.0" 0x19a0>)
frame-initialize()
# bind (debugger debug-on-error command-line-args-left)
command-line()
# (unwind-protect ...)
normal-top-level()
# (condition-case ... . error)
# (catch top-level ...)
Bus error
$ gdb ./xemacs
HP gdb 1.1
Copyright 1986 - 1999 Free Software Foundation, Inc.
Hewlett-Packard Wildebeest 1.1 (based on GDB 4.17-hpwdb-980821)
Wildebeest 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 Wildebeest. Type "show warranty" for details.
Wildebeest was built for PA-RISC 1.1 or 2.0 (narrow), HP-UX 10.20.
..
(gdb) r -q -vanilla
Starting program:
/bigfs1/compat/mina/cD0d1s0/darrylo/gnu/outside-XEmacs/xemacs-21.2/src/./xemacs -q
-vanilla
Program received signal SIGBUS, Bus error.
0x1b7930 in update_subwindow_cachel_data (f=0x40354400, subwindow=1077712384,
cachel=0x0) at glyphs.c:3636
3636 cachel->subwindow = subwindow;
(gdb) where
#0 0x1b7930 in update_subwindow_cachel_data (f=0x40354400,
subwindow=1077712384, cachel=0x0) at glyphs.c:3636
#1 0x1b7c68 in update_subwindow_cachel (subwindow=1077712384) at glyphs.c:3696
#2 0x1b8b78 in Fresize_subwindow (subwindow=1077712384, width=3571,
height=1074624516) at glyphs.c:4011
#3 0xda7ec in Ffuncall (nargs=4, args=0x7b03cbe4) at eval.c:3189
#4 0x7d3dc in execute_optimized_program (
program=0x7b03c910 "{\003\311\004{\003\310\374", stack_depth=7,
constants_data=0x7b03cbe4) at bytecode.c:747
l#5 0x7b03cbfc in ?? ()
#6 0x1b7c68 in update_subwindow_cachel
(subwindow=1074624516) at glyphs.c:3696
#7 0x40076448 in DS$symbols ()
#8 0x1b7c68 in update_subwindow_cachel (subwindow=1074624516) at glyphs.c:3696
#9 0x400d7804 in ?? ()
#10 0x1b7c68 in update_subwindow_cachel (subwindow=
Cannot access memory at address 0x1ffff9c.
) at glyphs.c:3696
Cannot access memory at address 0x1ffffac.
(gdb) l
3631
3632 static void
3633 update_subwindow_cachel_data (struct frame *f, Lisp_Object subwindow,
3634 struct subwindow_cachel *cachel)
3635 {
3636 cachel->subwindow = subwindow;
3637 cachel->width = XIMAGE_INSTANCE_SUBWINDOW_WIDTH (subwindow);
3638 cachel->height = XIMAGE_INSTANCE_SUBWINDOW_HEIGHT (subwindow);
3639 cachel->updated = 1;
3640 }
(gdb) p cachel
$1 = (struct subwindow_cachel *) 0x0
(gdb) q
The program is running. Exit anyway? (y or n) y
$
========================================================================
Contents of Installation:
========================================================================
uname -a: HP-UX mina B.10.20 A 9000/780 2009601751 two-user license
./configure '--x-includes=/usr/include/X11R6'
'--site-includes=/opt/hpeesofRD/include'
'--site-libraries=/opt/hpeesofRD/lib' '--cflags=-g +DAportable'
XEmacs 21.2-b19 "Shinjuku" configured for `hppa2.0-hp-hpux10.20'.
Where should the build process find the source code?
/users/darrylo/d0/gnu/outside-XEmacs/xemacs-21.2
What installation prefix should install use? /usr/local
What operating system and machine description files should XEmacs use?
`s/hpux10.h' and `m/hp800.h'
What compiler should XEmacs be built with? cc -g +DAportable
Should XEmacs use the GNU version of malloc? yes
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/dt/include
/usr/include/X11R6 /usr/contrib/X11R6/include
Where do we find X Windows libraries? /usr/dt/lib /usr/lib/X11R6
/usr/contrib/X11R6/lib
Additional header files: /opt/hpeesofRD/include
Additional libraries: /opt/hpeesofRD/lib
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 support for X-Face message headers.
Compiling in support for Berkeley DB.
Compiling in support for DBM.
Compiling in support for CDE.
Compiling in support for ToolTalk.
Compiling in EXPERIMENTAL support for Drag'n'Drop ( CDE ).
Compiling in support for proper WM_COMMAND handling.
Using Lucid menubars.
Using Lucid scrollbars.
Using Motif native widgets.
Using Motif dialog boxes.
Compiling in DSO module support.
movemail will use "dot-locking" for locking mail spool files.
Compiling in extra code for debugging.
WARNING: ---------------------------------------------------------
WARNING: Compiling in support for runtime error checking.
WARNING: XEmacs will run noticeably more slowly as a result.
WARNING: Error checking is on by default for XEmacs beta releases.
WARNING: ---------------------------------------------------------
========================================================================
--
Darryl Okahata
darrylo(a)sr.hp.com
DISCLAIMER: this message is the author's personal opinion and does not
constitute the support, opinion, or policy of Hewlett-Packard, or of the
little green men that have been following him all day.