From: Alan Braslau <alan.braslau@cea.fr>
To: Hans Hagen <pragma@wxs.nl>
Cc: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: strange crash
Date: Thu, 16 Feb 2017 13:54:01 -0700 [thread overview]
Message-ID: <20170216135401.6af851b9@zoo.hsd1.co.comcast.net> (raw)
In-Reply-To: <cc0fa224-525e-8d07-6b4a-6e8ea214f8c4@gmx.es>
On Thu, 16 Feb 2017 21:40:40 +0100
Pablo Rodriguez <oinos@gmx.es> wrote:
> On 02/16/2017 07:51 PM, j. van den hoff wrote:
> > hi,
> > in a pristine standalone context (installed yesterday) under ubuntu
> > I see a seemingly consistent crash of luatex if the document
> > contains footnotes [...]
> > while without the footnote it does compile just fine (the same
> > happens in more complicated documents: crashes until last footnote
> > is removed, then it compiles...). I am not an experienced context
> > user, but don't see that I could have done much wrong in installing
> > context in the first place (notably, the search path seems
> > correct). any idea what's going on here?
>
> Weird, I can compile your sample in Linux32.
On a fresh download of the Standalone, and using a new luatex binary
just compiled on the linux 32bit machine, I get the following:
tex error > tex error on line 1 in file /root/foo.tex: ! Infinite
glue shrinkage inserted from \skip131
\page ->\par
\dosingleempty \page_breaks_process
\strc_pagenumbers_flush_final_page ...\else \page
[\p_strc_pagenumbers_page ...
\dostoptext ...\strc_pagenumbers_flush_final_page
\page \the
\everystoptext ... l.1 \dostoptext
\clf_stoptext ->\luafunction \16>>clf_stoptext
l.3 \stoptext
1 >> \starttext
2 foo\footnote{bar}
3 \stoptext
4
___________________________________________________________________________________
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://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2017-02-16 20:54 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-16 18:51 j. van den hoff
2017-02-16 19:32 ` Alan Braslau
2017-02-16 19:36 ` j. van den hoff
2017-02-16 20:04 ` Marcus Vinicius Mesquita
2017-02-16 20:40 ` Pablo Rodriguez
2017-02-16 20:54 ` Alan Braslau [this message]
2017-02-16 20:56 ` j. van den hoff
2017-02-16 21:20 ` Pablo Rodriguez
2017-02-16 21:32 ` j. van den hoff
2017-02-16 21:51 ` Pablo Rodriguez
2017-02-16 22:02 ` Alan Braslau
2017-02-17 9:13 ` Hans Hagen
2017-02-17 9:28 ` Hans Hagen
2017-02-17 10:13 ` strange crash -- SOLVED j. van den hoff
2017-02-17 10:45 ` strange crash Peter Rolf
2017-02-17 13:30 ` luigi scarso
2017-02-17 13:41 ` Peter Rolf
2017-02-18 9:32 ` Lutz Haseloff
2017-02-18 9:50 ` luigi scarso
2017-02-18 10:00 ` Lutz Haseloff
2017-02-18 10:45 ` luigi scarso
2017-02-18 10:59 ` Lutz Haseloff
2017-02-18 11:06 ` luigi scarso
2017-02-18 11:49 ` Lutz Haseloff
2017-02-18 11:55 ` luigi scarso
2017-02-18 13:11 ` Lutz Haseloff
2017-02-18 12:15 ` luigi scarso
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=20170216135401.6af851b9@zoo.hsd1.co.comcast.net \
--to=alan.braslau@cea.fr \
--cc=ntg-context@ntg.nl \
--cc=pragma@wxs.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).