* Malcolm Agnew <malcolm.agnew(a)t-online.de> writes:
I just edit a file (say Makefile), scroll in the file for a few
seconds and CRASH.
This sounds like a similar problem that I was having with 21.5 a while
back. I tracked it down to `lookup-syntax-properties', if I set it to
`nil' I'd get crashes when trying to scroll large-ish fontified
buffers (usually cperl-mode).
Try setting `lookup-syntax-properties' to `t' (if it's `nil') and see
if that helps.
As I said before "Is there anything I should do to help track
this
bug?"
Start with `xemacs -no-autoloads' and see if you can reproduce the
crash with that. You probably won't be able to because I'm betting
that it is font-lock related.
Next, try with `xemacs -vanilla'. If you still can't reproduce the
crash, eval each sexp in your ~/.xemacs/init.el until you can.
Hopefully you know your way around gdb better than I do, so...
$ cd /path/to/xemacs-build-dir/src/
$ gdb ./xemacs | tee /tmp/outputfile
(gdb) run -vanilla
eval that suspect form from ~/.xemacs/init.el in the "gdb started
XEmacs" and then reproduce the crash.
At this point come back to gdb and do `lbt' which'll give you a lisp
backtrace. Do `bt' for a C backtrace. Now, unfortunately, this is
where I get lost, but there are some gdb macros (already loaded into
gdb because you started it from the src directory that has a
`.gdbinit' file for this purpose) that you can use to inspect the
values and names of the things in the C trace.
I don't know if any of that will be of much help to you, but maybe
it'll be enough to at least get you started.
--
|---<Steve Youngs>---------------<GnuPG KeyID: A94B3003>---|
| XEmacs - The only _______ you'll ever need. |
| Fill in the blank, yes, it's THAT good! |
|------------------------------<sryoungs(a)bigpond.net.au>---|