On 8/15/20 8:14 PM, Pablo Rodriguez wrote:
> On 8/15/20 7:23 PM, Hans Hagen wrote:
>> On 8/15/2020 5:25 PM, Pablo Rodriguez wrote:
>>
>>> Which is the meaning of error number 139? It might help me to know what
>>> I should be looking at.
>>> Hm, but does the current version also quit? I fixed a mp
On 8/15/20 7:23 PM, Hans Hagen wrote:
> On 8/15/2020 5:25 PM, Pablo Rodriguez wrote:
>
>> Which is the meaning of error number 139? It might help me to know what
>> I should be looking at.
>
> Hm, but does the current version also quit? I fixed a mp issue.
Since my source is huge, I might need to
On 8/15/20 7:23 PM, Hans Hagen wrote:
> On 8/15/2020 5:25 PM, Pablo Rodriguez wrote:
>
>> Which is the meaning of error number 139? It might help me to know what
>> I should be looking at.
>> Hm, but does the current version also quit? I fixed a mp issue.
The version that works for me is
On 8/15/2020 5:25 PM, Pablo Rodriguez wrote:
Which is the meaning of error number 139? It might help me to know what
I should be looking at.
Hm, but does the current version also quit? I fixed a mp issue.
Hans
-
On 8/14/20 9:47 AM, Hans Hagen wrote:
> On 8/14/2020 9:26 AM, Pablo Rodriguez wrote:
>
>> Latest from 2020.08.11 works fine for my huge document, but current
>> latest (from today) breaks compilation. So I use latest from 2020.08.11.
>
> i really need a MWE example then .. all runs well here
Hello Lutz,
I can confirm this. Compiling luametafun.tex (see luametafun.zip; I
included the log-file, but the log-file doesn't include all the output I
can see on the console (therefore I included the file output_console.txt
with a copy of my console-output). I used linux aarch64.
Yes,
On 8/14/2020 1:38 PM, Lutz Haseloff wrote:
Hi all
I have a similar problem compiling luametafun.tex in the doc sources.
It fails with different errorcodes on win64 and linux aarch64. On linux
aarch64 i get a bonus "Segmentation fault".
I append the console outputs of the context runs.
If i
Hi Wolfgang,
thats a little bit difficult, because the error apparently happens at a
random position in the document (you can add a syntax error in the
document an change the position of the syntax error in the document
until lmtx crashes before it detects the error to get the paragraph
where
Hello Pablo,
thank you for your suggestions, but I don't use LMTX productively, so I
have no problem with a broken LMTX-version. I only use it to check
whether there are breaking changes in LMTX by typesetting all of my
documents with the newest LMTX-version (to see if I need to change them
in
Hello Pablo,
thank you for your suggestions, but I don't use LMTX productively, so I
have no problem with a broken LMTX-version. I only use it to check
whether there are breaking changes in LMTX by typesetting all of my
documents with the newest LMTX-version (to see if I need to change them
in
Hello Hans,
I get the error with the newest upload too.
Jannik
Am 14.08.20 um 08:47 schrieb Hans Hagen:
> On 8/14/2020 2:38 AM, Jannik Voges wrote:
>>
>> Hello,
>>
>>
>> I have a similar problem with long context-documents (but not all long
>> context-documents are affected and I don't
Hi all
I have a similar problem compiling luametafun.tex in the doc sources.
It fails with different errorcodes on win64 and linux aarch64. On linux aarch64
i get a bonus "Segmentation fault".
I append the console outputs of the context runs.
If i comment out the input of luametafun-axis and
On 8/14/2020 11:41 AM, Jannik Voges wrote:
Hello Pablo,
thank you for your suggestions, but I don't use LMTX productively, so I
have no problem with a broken LMTX-version. I only use it to check
whether there are breaking changes in LMTX by typesetting all of my
documents with the newest
Jannik Voges schrieb am 14.08.2020 um 11:29:
Hello Hans,
I get the error with the newest upload too.
You have to provide a minimal example which produces the error.
Wolfgang
___
If your question is of interest
On 8/14/2020 9:26 AM, Pablo Rodriguez wrote:
Latest from 2020.08.11 works fine for my huge document, but current
latest (from today) breaks compilation. So I use latest from 2020.08.11.
i really need a MWE example then .. all runs well here
Hans
On 8/14/20 8:47 AM, Hans Hagen wrote:
> On 8/14/2020 2:38 AM, Jannik Voges wrote:
>> [...]
>> 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 8/14/2020 2:38 AM, Jannik Voges wrote:
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
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
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
19 matches
Mail list logo
