core dump doing practically anything to region.
This one is _really_ annoying.
I'm getting core dumps anytime I do something to a region.
Recipe for crash:
C-SPC
move point somewhere to create a region
C-w (M-w works just as well, even M-x boxquote-region)
CRASH!
Okay, I don't know anything about gdb (never been inspired enough to
learn), but here's what I've been able to dredge up. I apologise if
it's not useful.
Current directory is /usr/local/bin/
GNU gdb 5.0
Copyright 2000 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-slackware-linux"...
(gdb) core-file ~/core
warning: core file may not match specified executable file.
Core was generated by `xemacs'.
Program terminated with signal 6, Aborted.
Cannot access memory at address 0x40018e30
#0 0x403322e1 in ?? ()
(gdb) Starting program: /usr/local/bin/xemacs-21.2-b44
Cannot access memory at address 0x40018e30
(gdb) Continuing.
Cannot access memory at address 0x40018e30
(gdb) Continuing.
Fatal error: assertion failed, file lisp.h, line 1397, RECORD_TYPEP (obj,
lrecord_type_marker)
Program received signal SIGABRT, Aborted.
0x403322e1 in __kill () from /lib/libc.so.6
(gdb) Continuing.
Fatal error (6).
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-21.2-b44 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:
call-interactively(kill-region)
# (condition-case ... . error)
# (catch top-level ...)
Program received signal SIGABRT, Aborted.
0x403322e1 in __kill () from /lib/libc.so.6
(gdb) Continuing.
Program terminated with signal SIGABRT, Aborted.
The program no longer exists.
(gdb)
--
|---<Steve Youngs>---------------<GnuPG KeyID: 9E7E2820>---|
| XEmacs - It's not just an editor. |
| It's a way of life. |
|------------------------------------<youngs(a)xemacs.org>---|