A document that runs fine under ConTeXt ver: 2015.10.09 21:28 MKIV beta fmt: 2015.10.11 int: english/english suddenly doesn't under ConTeXt ver: 2015.12.22 10:50 MKIV beta fmt: 2015.12.27 int: english/english mtx-context | fatal error: no return code, message: luatex: execution interrupted
Loaded this beta today. The previous beta runs ok, the new beta gives the error. The pdf produced in the latter seems at fault. Anyone knows how this error can occur?
A further observationthat makes things seem far worse: the error is dependent on the content! The document in question has several chapters, each in a separate file. Dependent on the combination of files included, the error does or does not show up. Sofar I cannot find a pattern linked to the error. Making a minimal example proved impossible, alas.
Hans van der meer
On 27 Dec 2015, at 13:19, dr. Hans van der Meer havdmeer@ziggo.nl wrote:
A document that runs fine under ConTeXt ver: 2015.10.09 21:28 MKIV beta fmt: 2015.10.11 int: english/english suddenly doesn't under ConTeXt ver: 2015.12.22 10:50 MKIV beta fmt: 2015.12.27 int: english/english mtx-context | fatal error: no return code, message: luatex: execution interrupted
Loaded this beta today. The previous beta runs ok, the new beta gives the error. The pdf produced in the latter seems at fault. Anyone knows how this error can occur?
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 ___________________________________________________________________________________
Earlier I posted the following error:
A document that runs fine under ConTeXt ver: 2015.10.09 21:28 MKIV beta fmt: 2015.10.11 int: english/english suddenly doesn't under ConTeXt ver: 2015.12.22 10:50 MKIV beta fmt: 2015.12.27 int: english/english mtx-context | fatal error: no return code, message: luatex: execution interrupted
At first I thought this was due to a new version of ConTeXt. A mistake, it now seems. I encounter the same error in an earlier version. It seems therefore a problem already present in either LuaTeX or ConTeXt.
The error must be related to the placement of floats witness the following fact, typesetting the same document with only a difference in float-placement:
No error: \startplacetable[location=here,reference=tab:beaufort,title=Beaufort tabel] Error: \startplacetable[location=page,reference=tab:beaufort,title=Beaufort tabel]
A further observation: the item placed is nearly filling the page. Making the item somewhat smaller avoids the error, even if its the only item on the page.
I did not succeed to compose a minimal example, in my experience the occurrence of the error seems too unpredictable. The actual project is far to complex and too big to be of use for debugging.
I sincerely hope someone can solve this. The error brings to mind a similar problem experienced years earlier. It then was a problem of a null object in the pdf-section, if my memory is correct and I think Taco has solved that.
Hans van der Meer
On Tue, Jan 12, 2016 at 7:49 PM, dr. Hans van der Meer havdmeer@ziggo.nl wrote:
Earlier I posted the following error:
A document that runs fine under ConTeXt ver: 2015.10.09 21:28 MKIV beta fmt: 2015.10.11 int: english/english suddenly doesn't under ConTeXt ver: 2015.12.22 10:50 MKIV beta fmt: 2015.12.27 int: english/english mtx-context | fatal error: no return code, message: luatex: execution interrupted
At first I thought this was due to a new version of ConTeXt. A mistake, it now seems. I encounter the same error in an earlier version. It seems therefore a problem already present in either LuaTeX or ConTeXt.
The error must be related to the placement of floats witness the following fact, typesetting the same document with only a difference in float-placement:
No error: \startplacetable[location=here,reference=tab:beaufort,title=Beaufort tabel] Error: \startplacetable[location=page,reference=tab:beaufort,title=Beaufort tabel]
A further observation: the item placed is nearly filling the page. Making the item somewhat smaller avoids the error, even if its the only item on the page.
I did not succeed to compose a minimal example, in my experience the occurrence of the error seems too unpredictable. The actual project is far to complex and too big to be of use for debugging.
I sincerely hope someone can solve this. The error brings to mind a similar problem experienced years earlier. It then was a problem of a null object in the pdf-section, if my memory is correct and I think Taco has solved that.
Hans van der Meer
hard to say without an example. \loggingall can help, but it can generate a huge amount of data. Using \loggingall near the error is better, but of course it means that you know more or less where it happens.
On 12 Jan 2016, at 20:11, luigi scarso <luigi.scarso@gmail.commailto:luigi.scarso@gmail.com> wrote:
hard to say without an example. \loggingall can help, but it can generate a huge amount of data. Using \loggingall near the error is better, but of course it means that you know more or less where it happens.
I have an idea where to start and stop logging.
Is just \loggingall sufficient to start the log? How do I stop that logging?
Hans van der Meer
-
dr. Hans van der Meer -
luigi scarso -
Meer, Hans van der