ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: luigi scarso <luigi.scarso@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: LuaTeX Crashes
Date: Fri, 10 Oct 2014 00:56:38 +0200	[thread overview]
Message-ID: <CAG5iGsAzBF-th3bttVeaF2yRSk0+ObNDjENt0VL3A=bbFXXmRw@mail.gmail.com> (raw)
In-Reply-To: <CAANrE7p+LRmfHT6ygvU-mopMfjJgFEVzvynHHxoO8anZzitUnQ@mail.gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 1659 bytes --]

On Fri, Oct 10, 2014 at 12:36 AM, Thangalin <thangalin@gmail.com> wrote:

> Hi,
>
> This Heisenbug was arduous to nail down. The following code causes the
> stack overflow on the first run:
>
> http://pastebin.com/raw.php?i=qwGGBrJf
>
> If the file is changed to compile successfully, then the compile will
> succeed on subsequent attempts, even if the changes are reverted to
> the original state. It only breaks on the first try. Something must be
> cached, but I don't know what.
>
> $ context --version
> mtx-context     | current version: 2014.10.07 11:14
>
> $ luatex --version
> This is LuaTeX, Version beta-0.79.1 (TeX Live 2014/dev) (rev 4972)
>
> $ uname -a
> Linux 3.13.0-36-generic #63-Ubuntu SMP Wed Sep 3 21:30:07 UTC 2014
> x86_64 x86_64 x86_64 GNU/Linux
>
> There might be some extraneous bits, but hopefully that will be enough
> of a clue as to the problem.
>
> ___________________________________________________________________________________
> 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
>
> ___________________________________________________________________________________
>

no crash here
current version: 2014.10.09 15:22



$ luatex --version
This is LuaTeX, Version beta-0.79.1 (TeX Live 2014/dev) (rev 4972)



$ uname -a
Linux  3.14.1-031401-generic #201404141220 SMP Mon Apr 14 16:21:48 UTC 2014
x86_64 x86_64 x86_64 GNU/Linux



-- 
luigi

[-- Attachment #1.2: Type: text/html, Size: 2867 bytes --]

[-- Attachment #2: Type: text/plain, Size: 485 bytes --]

___________________________________________________________________________________
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
___________________________________________________________________________________

  reply	other threads:[~2014-10-09 22:56 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-08 22:14 Thangalin
2014-10-09  6:41 ` luigi scarso
2014-10-09  6:51 ` Hans Hagen
2014-10-09 22:36   ` Thangalin
2014-10-09 22:56     ` luigi scarso [this message]
  -- strict thread matches above, loose matches on Subject: below --
2014-01-21 15:40 luatex crashes Henning Hraban Ramm
2014-01-21 16:49 ` Henning Hraban Ramm
2014-01-21 17:02   ` Mojca Miklavec
2014-01-21 17:05     ` Hans Hagen
2014-01-21 17:29   ` Henning Hraban Ramm

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='CAG5iGsAzBF-th3bttVeaF2yRSk0+ObNDjENt0VL3A=bbFXXmRw@mail.gmail.com' \
    --to=luigi.scarso@gmail.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).