ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Jannik Voges <researchjavo@icloud.com>
To: ntg-context@ntg.nl
Subject: Re: compilation error in LMTX
Date: Fri, 14 Aug 2020 02:38:46 +0200	[thread overview]
Message-ID: <906717a1-836a-8e79-bb82-6d2b143c925f@icloud.com> (raw)
In-Reply-To: <990aa277-47bc-6116-423c-b815765bfc14@gmx.es>

[-- Attachment #1: Type: text/plain, Size: 1973 bytes --]


Hello,


I have a similar problem with long context-documents (but not all long
context-documents are affected and I don't know what triggers the
error). Sometimes, the errors (error code 139) are happening on second
or third runs (but it might happen on first runs too). When I remove the
chapter where the error happens and all later chapters from the document
it might happen, that the error occures in an earlier chapter.
In addition to that, documents, which had this error yesterday, can now
be compiled without the problem and other documents without the error
yesterday have the error today. Its really strange.


Thanks to all,

Jannik


Am 13.08.20 um 12:49 schrieb Pablo Rodriguez:
> Dear list,
> 
> compiling a huge XML document (output PDF > 1200 pages), I get the
> following error with latest current (2020.08.11 15:59):
> 
>   pages           > flushing realpage 187, userpage 187, subpage 3
>   mtx-context     | fatal error: return code: 139
>   Compilation failed.
> 
> Some hints about what I cannot avoid considering a cryptic error message:
> 
> 1. There is no previous warning when compiling previous pages.
> 1. The compulation error appears on the third run.
> 1. ConTeXt latest from 2020.08.07 23:37 compiles this just fine.
> 
> Sorry, there is no minimal sample here. Any ideas about this? Or at
> least, any chances for the source that is breaking compilation?
> 
> Many thanks for your help,
> 
> Pablo
> --
> http://www.ousia.tk
> ___________________________________________________________________________________
> 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
> ___________________________________________________________________________________
> 

[-- Attachment #2: 0x805A4918E8698418.asc --]
[-- Type: application/pgp-keys, Size: 677 bytes --]

[-- Attachment #3: Type: text/plain, Size: 493 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://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki     : http://contextgarden.net
___________________________________________________________________________________

  reply	other threads:[~2020-08-14  0:38 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-13 10:49 Pablo Rodriguez
2020-08-14  0:38 ` Jannik Voges [this message]
2020-08-14  6:47   ` Hans Hagen
2020-08-14  7:26     ` Pablo Rodriguez
2020-08-14  7:47       ` Hans Hagen
2020-08-15 15:25         ` Pablo Rodriguez
2020-08-15 17:23           ` Hans Hagen
2020-08-15 18:14             ` Pablo Rodriguez
2020-08-15 21:54               ` Pablo Rodriguez
2020-08-15 18:51             ` Pablo Rodriguez
2020-08-14  9:40       ` Jannik Voges
2020-08-14  9:41       ` Jannik Voges
2020-08-14 11:04         ` Hans Hagen
2020-08-14 11:38           ` Lutz Haseloff
2020-08-14 12:56             ` Jannik Voges
2020-08-14 14:11             ` Hans Hagen
2020-08-14  9:29     ` Jannik Voges
2020-08-14  9:33       ` Wolfgang Schuster
2020-08-14  9:59         ` Jannik Voges

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=906717a1-836a-8e79-bb82-6d2b143c925f@icloud.com \
    --to=researchjavo@icloud.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).