On 03/15/2011 03:44 PM, Steffen Wolfrum wrote:

Am 15.03.2011 um 11:27 schrieb Steffen Wolfrum:


Am 15.03.2011 um 10:07 schrieb Vnpenguin:


Best wishes,
Taco

Not here:
\starttext
\dorecurse{5000} {\input knuth \page }
\stoptext
pages>  flushing realpage 3987, userpage 3987
PANIC: unprotected error in call to Lua API (stack overflow (out of
stack space))

mtx-context     | fatal error: return code: 1
with latest minimals.


I have exactely same error as you on Linux x86_64 CentOS , luatex
beta-0.65.0-2010121316

However on my Windows XP (always with Minimals distro) I can compile
without error. On Windows I have :
E:\User\xxx\tex>luatex --version
This is LuaTeX, Version beta-0.66.0-2011021923 (Web2C 2010) (rev 4086)

Maybe luatex of Linux 64bit is out-of-date ?


Just update luatex to beta-0.66.0-2011031509 (rev 4090) and now I got
5000-pages PDF :)


I also updated now [got beta-0.66.0-2011031511 (rev 4090)]
but still my project gives a PANIC!

I'll try now to boil down a minimal example out of my chapters ...


Four hours later:
Still I do not have a "minimal" example. But I think I have an idea what might 
be the problem:
The number of footnotes seems to have an impact.
I boiled it down to a version of my project where just a little additional note 
causes PANIC.
Adding another page of text or a sectioning heading or anything else is fine.

Does this help further finding the bug?

Not really, sorry. Unless the problem gets worse if you add extra footnotes earlier?

Does it make sense to have compare both tuc files (the last working and the 
first buggy)?

Probably not.

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
___________________________________________________________________________________

Reply via email to