|
From: | Andreas Schwab |
Subject: | Re: Certain numbers of special forms cause changing behaviour on function calls in --batch |
Date: | Sun, 10 Jul 2016 19:10:39 +0200 |
User-agent: | Gnus/5.13 (Gnus v5.13) Emacs/25.0.95 (gnu/linux) |
Eli Zaretskii <address@hidden> writes: > That's what I see, thanks. Very strange, this error from valgrind. > And we are none the wiser. --track-origins=yes gives more information. ==25255== Conditional jump or move depends on uninitialised value(s) ==25255== at 0x5F597E: MARKERP (lisp.h:2614) ==25255== by 0x5F597E: exec_byte_code (bytecode.c:1367) ==25255== by 0x5B4582: Ffuncall (eval.c:2754) ==25255== by 0x5F394C: exec_byte_code (bytecode.c:880) ==25255== by 0x5B4582: Ffuncall (eval.c:2754) ==25255== by 0x5F394C: exec_byte_code (bytecode.c:880) ==25255== by 0x5B336C: apply_lambda (eval.c:2794) ==25255== by 0x5B36B2: eval_sub (eval.c:2241) ==25255== by 0x5B3EEC: Fprogn (eval.c:426) ==25255== by 0x5B3BFC: eval_sub (eval.c:2119) ==25255== by 0x5B3BFC: eval_sub (eval.c:2119) ==25255== by 0x5B3EEC: Fprogn (eval.c:426) ==25255== by 0x5AD694: Fsave_excursion (editfns.c:1014) ==25255== Uninitialised value was created by a stack allocation ==25255== at 0x57942A: Fvertical_motion (indent.c:1993) One of the local variables of Fvertical_motion isn't properly initialized. Andreas. -- Andreas Schwab, address@hidden GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5 "And now for something completely different."
[Prev in Thread] | Current Thread | [Next in Thread] |