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

[Noam Postavsky]

On Sun, Jul 10, 2016 at 12:45 PM, Eli Zaretskii <address@hidden> wrote:
>> I don't think Fzerop is especially relevant, AFAICT, the error just
>> means Fzerop received an unitialized value as its first argument.
>
> Sorry, I;m not following: Fzerop is called from Ffuncall, i.e. from
> Lisp, so how can the value of Fzerop's argument be uninitialized?
> What am I missing?

Possibly there is an error in the bytecode interpreter? Is there an
easy way to trace pushes and pops to the stack?