From: Taco Hoekwater <taco@elvenkind.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Luatex crash on \endinput \end
Date: Fri, 18 May 2012 10:58:31 +0200 [thread overview]
Message-ID: <4FB60F37.7080208@elvenkind.com> (raw)
In-Reply-To: <alpine.LNX.2.02.1205171028470.1464@ybpnyubfg.ybpnyqbznva>
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.
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.
Best wishes,
Taco
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://tex.aanhet.net
archive : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2012-05-18 8:58 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-16 16:12 Aditya Mahajan
2012-05-16 16:42 ` luigi scarso
2012-05-16 23:06 ` Aditya Mahajan
2012-05-17 12:24 ` luigi scarso
2012-05-17 13:44 ` Taco Hoekwater
2012-05-17 14:30 ` Aditya Mahajan
2012-05-17 23:17 ` Vladimir Lomov
2012-05-18 8:58 ` Taco Hoekwater [this message]
2012-05-18 9:06 ` luigi scarso
2012-05-18 9:36 ` Aditya Mahajan
2012-05-18 9:44 ` Hans Hagen
2012-05-18 10:34 ` Taco Hoekwater
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4FB60F37.7080208@elvenkind.com \
--to=taco@elvenkind.com \
--cc=ntg-context@ntg.nl \
/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.
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 NNTP newsgroup(s).