Re: Certain numbers of special forms cause changing behaviour on function calls in --batch

[Eli Zaretskii]

> From: Andreas Schwab <address@hidden>
> Cc: Noam Postavsky <address@hidden>,  address@hidden,  address@hidden,  
> address@hidden,  address@hidden
> Date: Sun, 10 Jul 2016 19:10:39 +0200
> 
> --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.

Thanks.  Does the patch below fix the problem?

diff --git a/src/indent.c b/src/indent.c
index bc59239..ba6612b 100644
--- a/src/indent.c
+++ b/src/indent.c
@@ -2027,6 +2027,7 @@ whether or not it is currently displayed in some window.  
*/)
       struct position pos;
       pos = *vmotion (PT, PT_BYTE, XINT (lines), w);
       SET_PT_BOTH (pos.bufpos, pos.bytepos);
+      it.vpos = pos.vpos;
     }
   else
     {