Adrian Aichner <adrian(a)xemacs.org> writes:
It's the executable for which I sent a build report to
XEmacs Build Reports List <xemacs-buildreports(a)xemacs.org>
earlier today.
M-x toggle-profiling
Then I want to execute a command with C-u prefix, and BANG.
Ah, when I start vanilla it crashes immediately on
M-x toggle-profiling
Here are C and lisp backtrace
profile_record_just_called(backtrace * 0x0082fca4) line 273 + 35 bytes
Fdispatch_event(long 17300742) line 4646 + 21 bytes
condition_case_1(long -2097148532, long (long)* 0x03a804c4, long -397205899, long (long,
long)* 0x000d8c8d, long -998045558) line 1924 + 53 bytes
9ae8536f()
----------------------------------------------------------------------------
Fatal error.
Your files have been auto-saved.
Use `M-x recover-session' to recover them.
Your version of XEmacs was distributed with a PROBLEMS file that may describe
your crash, and with luck a workaround. Please check it first, but do report
the crash anyway.
Please report this bug by invoking M-x report-emacs-bug, or by selecting
`Send Bug Report' from the Help menu. If that won't work, send ordinary
email to `xemacs-beta(a)xemacs.org'. *MAKE SURE* to include this entire
output from this crash, especially including the Lisp backtrace, as well as
the XEmacs configuration from M-x describe-installation (or equivalently,
the file `Installation' in the top of the build tree).
If you are fortunate enough to have some sort of debugging aid installed
on your system, for example Visual C++, and you can get a C stack backtrace,
*please* include it, as it will make our life far easier.
Lisp backtrace follows:
# (unwind-protect ...)
# (unwind-protect ...)
# (unwind-protect ...)
# (unwind-protect ...)
# (unwind-protect ...)
# (unwind-protect ...)
# (unwind-protect ...)
# (condition-case ... . error)
# (catch top-level ...)
--
Adrian Aichner
mailto:adrianï¼ xemacs.org
http://www.xemacs.org/