[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: emacs-27 3bce7ec: CC Mode: Protect against consecutive calls to befo
From: |
Alan Mackenzie |
Subject: |
Re: emacs-27 3bce7ec: CC Mode: Protect against consecutive calls to before-change-functions ... |
Date: |
Wed, 4 Mar 2020 21:24:47 +0000 |
User-agent: |
Mutt/1.10.1 (2018-07-13) |
Hello, Glenn.
On Fri, Feb 28, 2020 at 11:54:23 -0500, Glenn Morris wrote:
> Alan Mackenzie wrote:
> > branch: emacs-27
> > commit 3bce7ec3826003fda1971224a20d7fe2cba8bf65
> > CC Mode: Protect against consecutive calls to before-change-functions
> > ...
> This causes srecode-utest-getset-output in
> test/lisp/cedet/srecode-utest-getset.el to fail:
> Test srecode-utest-getset-output backtrace:
> parse-partial-sexp(1 627 nil nil nil syntax-table)
> c-after-change-mark-abnormal-strings(100 320 0)
> #f(compiled-function (fn) #<bytecode 0x9b5689>)(c-after-change-mark-
> mapc(#f(compiled-function (fn) #<bytecode 0x9b5689>) (c-depropertize
> c-after-change(100 320 0)
> run-hook-with-args(c-after-change 100 320 0)
> srecode-insert-fcn(#<srecode-template getset-in-class> #<srecode-dic
> srecode-insert-getset()
> #f(compiled-function () #<bytecode 0x9573ad>)()
> ert--run-test-internal(#s(ert--test-execution-info :test #s(ert-test
> ert-run-test(#s(ert-test :name srecode-utest-getset-output :document
> ert-run-or-rerun-test(#s(ert--stats :selector (not (or ... ...)) :te
> ert-run-tests((not (or (tag :expensive-test) (tag :unstable))) #f(co
> ert-run-tests-batch((not (or (tag :expensive-test) (tag :unstable)))
> ert-run-tests-batch-and-exit((not (or (tag :expensive-test) (tag :un
> eval((ert-run-tests-batch-and-exit '(not (or (tag :expensive-test) (
> command-line-1(("-L" ":." "-l" "ert" "-l" "lisp/cedet/srecode-utest-
> command-line()
> normal-top-level()
> Test srecode-utest-getset-output condition:
> (args-out-of-range #<buffer srecode-utest-getset-TkO46e.cpp> 1 627)
> FAILED 1/1 srecode-utest-getset-output (1.709802 sec)
Yes. I've fixed this bug in the emacs-27 branch.
As a matter of interest, the scenario Mattias reported was caused by a
different bug (also fixed).
--
Alan Mackenzie (Nuremberg, Germany).