Mercurial > hg > xemacs-beta
view lib-src/config.values.in @ 5040:3daf9fc57cd4
fixes to test harness to allow backtracing/debugging of failures
-------------------- ChangeLog entries follow: --------------------
tests/ChangeLog addition:
2010-02-20 Ben Wing <ben@xemacs.org>
* automated/test-harness.el:
* automated/test-harness.el (test-harness-bug-expected): New.
* automated/test-harness.el (test-harness-unexpected-error-enter-debugger): New.
* automated/test-harness.el (test-harness-assertion-failure-enter-debugger): New.
* automated/test-harness.el (test-harness-unexpected-error-show-backtrace): New.
* automated/test-harness.el (test-harness-assertion-failure-show-backtrace): New.
* automated/test-harness.el (test-harness-assertion-failure-do-debug): New.
* automated/test-harness.el (test-harness-unexpected-error-do-debug): New.
* automated/test-harness.el (test-harness-unexpected-error-condition-handler): New.
* automated/test-harness.el (test-harness-error-wrap): New.
* automated/test-harness.el (test-harness-from-buffer):
New variables that allow a backtrace to be displayed and/or the
debugger to be entered when an assertion failure or unexpected error
occurs. By default, debugging occurs when interactive and debug-on-error
is set, and backtrace-displaying occurs either
(a) when stack-trace-on-error is set, or (b) always, when an unexpected
error occurs. (However, no backtracing or debugging occurs when a bug
is expected.)
| author | Ben Wing <ben@xemacs.org> |
|---|---|
| date | Sat, 20 Feb 2010 20:04:44 -0600 |
| parents | 772c80e0e180 |
| children |
line wrap: on
line source
;;; Do not edit this file! ;;; This file was automatically generated, by the config.values.sh script, ;;; from configure, which was itself automatically generated from configure.in. ;;; ;;; See lisp/config.el for details on how this file is used. ;;; ;;; You are trapped in a twisty maze of strange-looking files, all autogenerated... ;;; configure is created, from configure.in, by autoconf ;;; config.values.in is created, from configure, by config.values.sh ;;; config.values is created, from config.values.in, by configure ;;; config.values is read by lisp/config.el, ;;; to create the (Lisp object) config-value-hash-table ;;; Variables defined in configure by AC_SUBST follow: ;;; (These are used in Makefiles) ;;; Variables defined in configure by AC_DEFINE and AC_DEFINE_UNQUOTED follow: ;;; (These are used in C code)
