Will do, thanks Jan.
- Phil
Jan Vroonhof writes:
"Philip Aston" <paston(a)bea.com> writes:
> Can anyone comment on the stack trace provided with the original
> report? Maybe someone can guess what happened between 21.5-b1 and
> 21.5b2 to cause this?
Unfortunately that period is both long and contained some quite
substantial low-level rewrites by ben.
I understand from the backtrace that can run XEmacs under a debugger.
Then do the following
1. Make sure you have a full debugging and error checking XEmacs (as
is default in the beta builds).
2. Run XEmacs under the debugger.
3. Just before executing the command that triggers the crash break
into the debugger and set the global variable always_gc=1.
[XEmacs will be come reaaaaaaaally slow at this point.
4. Do the problematic command.
XEmacs will hopefull crash more predictably now & closer to the real
point. Try to get C & lisp back traces.
Jan