From: Andreas Schwab <schwab@linux-m68k.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: michael_heerdegen@web.de, yasushi.shoji@gmail.com,
me@wilfred.me.uk, emacs-devel@gnu.org,
Noam Postavsky <npostavs@users.sourceforge.net>
Subject: Re: Certain numbers of special forms cause changing behaviour on function calls in --batch
Date: Sun, 10 Jul 2016 19:10:39 +0200 [thread overview]
Message-ID: <87r3b12zcg.fsf@linux-m68k.org> (raw)
In-Reply-To: <83vb0de91c.fsf@gnu.org> (Eli Zaretskii's message of "Sun, 10 Jul 2016 19:45:51 +0300")
Eli Zaretskii <eliz@gnu.org> 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, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
next prev parent reply other threads:[~2016-07-10 17:10 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-26 16:39 Certain numbers of special forms cause changing behaviour on function calls in --batch Wilfred Hughes
2016-06-28 21:12 ` Michael Heerdegen
2016-06-29 16:23 ` Eli Zaretskii
2016-06-29 20:39 ` Michael Heerdegen
2016-06-30 2:38 ` Eli Zaretskii
2016-06-30 12:34 ` Michael Heerdegen
2016-06-30 15:19 ` Eli Zaretskii
2016-06-30 21:10 ` Michael Heerdegen
2016-07-01 7:21 ` Eli Zaretskii
2016-07-05 21:21 ` Michael Heerdegen
2016-07-05 21:33 ` Michael Heerdegen
2016-07-06 14:30 ` Eli Zaretskii
2016-07-06 14:47 ` Michael Heerdegen
2016-07-06 15:04 ` Eli Zaretskii
2016-07-10 10:34 ` Yasushi SHOJI
2016-07-10 11:13 ` Yasushi SHOJI
2016-07-10 11:33 ` Noam Postavsky
2016-07-10 14:53 ` Eli Zaretskii
2016-07-10 16:23 ` Noam Postavsky
2016-07-10 16:45 ` Eli Zaretskii
2016-07-10 17:03 ` Noam Postavsky
2016-07-10 17:29 ` Eli Zaretskii
2016-07-10 17:10 ` Andreas Schwab [this message]
2016-07-10 17:37 ` Eli Zaretskii
2016-07-10 18:40 ` Paul Eggert
2016-07-10 19:09 ` Eli Zaretskii
2016-07-10 17:37 ` Andreas Schwab
2016-07-10 18:02 ` Eli Zaretskii
[not found] ` <<83inwde5gv.fsf@gnu.org>
2016-07-10 18:20 ` Drew Adams
2016-07-10 21:44 ` Clément Pit--Claudel
2016-07-06 14:28 ` Eli Zaretskii
2016-06-30 5:58 ` Andreas Röhler
2016-06-30 15:13 ` Eli Zaretskii
2016-06-30 17:20 ` Andreas Röhler
2016-06-30 17:40 ` Eli Zaretskii
2016-06-30 21:22 ` Michael Heerdegen
2016-07-01 7:13 ` Eli Zaretskii
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87r3b12zcg.fsf@linux-m68k.org \
--to=schwab@linux-m68k.org \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=me@wilfred.me.uk \
--cc=michael_heerdegen@web.de \
--cc=npostavs@users.sourceforge.net \
--cc=yasushi.shoji@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).