On Fri, 18 May 2012, Taco Hoekwater wrote:
On 05/17/2012 04:30 PM, Aditya Mahajan wrote:
with the same crash. Can someone else using context minimals with archlinux check if they get a crash or not?
I get a crash (double free) with:
echo '\endinput \end ' | context --pipe
and I get a 'normal' Fatal error occurred with:
echo '\\endinput \\end' | context --pipe
and I think that solves that bit of the mystery.
Of all the differences in the systems, the most relevant was how the shell espace in string works. Apparently I have some weird option set in my .zshrc due to which echo always enable escape characters.
Now for that double-free:
echo '\tracingall \endinput \end ' | context --pipe
ends with:
{\endinput}
\end ->\ctxcommand {forceendjob()}
\ctxcommand #1->\directlua \zerocount {commands.#1} #1<-forceendjob() {\directlua} system > don't use \end to finish a document *** glibc detected *** luatex: double free or corruption (fasttop): 0x0000000004c21340 ***
It probably crashes because in context the \end code and the \endinput code interfere with eachother. You get the same crash if you create a simple input file with just that same line, and the crash goes away if you put \endinput and \end on separate lines, and as far as I can tell, context always crashes if \endinput and \end/\stoptext are on the same line.
Thanks for the diagnosis. Aditya