From: Vladimir Lomov <lomov.vl@yandex.ru>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: [LMTX urgent] core keeps getting dumped after 2019.11.28 LMTX update
Date: Fri, 29 Nov 2019 19:39:14 +0800 [thread overview]
Message-ID: <20191129113914.GA869@smoon.bkoty.ru> (raw)
In-Reply-To: <5e9fef55-ffc1-7101-0c9e-a4f7cedaf704@xs4all.nl>
[-- Attachment #1.1: Type: text/plain, Size: 4200 bytes --]
Hello,
** Hans Hagen <j.hagen@xs4all.nl> [2019-11-29 10:34:31 +0100]:
> On 11/29/2019 7:32 AM, Floris van Manen wrote:
>> Anyone?
>>
>> After updating LMTX to the latest version 2019.11.28, context stopped
>> working, only to produce core dumps ...
>>
>> Any hints as how to resolve this?
> wipe the cache
Same here: Archlinux x86_64, luametatex 2019.11.28. I deleted
luatex-cache, run
$ mtxrun --generate; context --make
and on simplest example
--------------------------- 8< -----------------------------
\starttext
Hello, World!
\stoptext
--------------------------- 8< -----------------------------
I got
--------------------------- 8< -----------------------------
resolvers | formats | executing runner 'run luametatex format': /usr/local/opt/lmtx/tex/texmf-linux-64/bin/luametatex --jobname="simple" --fmt=/home/vladimir/.cache/lmtx/luatex-cache/context/5fe67e0bfe781ce0dde776fb1556f32e/formats/luametatex/cont-en.fmt --lua=/home/vladimir/.cache/lmtx/luatex-cache/context/5fe67e0bfe781ce0dde776fb1556f32e/formats/luametatex/cont-en.lui cont-yes.mkiv --c:currentrun=1 --c:fulljobname="./simple.tex" --c:input="./simple.tex" --c:kindofrun=1 --c:maxnofruns=9 --c:texmfbinpath="/usr/local/opt/lmtx/tex/texmf-linux-64/bin"
This is LuaMetaTeX, Version 2.01.0
open source > level 1, order 1, name 'cont-yes.mkiv'
system >
system > ConTeXt ver: 2019.11.28 14:27 MKIV beta fmt: 2019.11.29 int: english/english
system >
system > 'cont-new.mkiv' loaded
open source > level 2, order 2, name '/usr/local/opt/lmtx/tex/texmf-context/tex/context/base/mkiv/cont-new.mkiv'
system > beware: some patches loaded from cont-new.mkiv
close source > level 2, order 2, name '/usr/local/opt/lmtx/tex/texmf-context/tex/context/base/mkiv/cont-new.mkiv'
system > files > jobname 'simple', input './simple', result 'simple'
fonts > latin modern fonts are not preloaded
languages > language 'en' is active
open source > level 2, order 3, name './simple.tex'
fonts > preloading latin modern fonts (second stage)
fonts > otf loading > loading '/usr/local/opt/lmtx/tex/texmf/fonts/opentype/public/lm/lmroman12-regular.otf', hash 'lmroman12-regular'
fonts > otf loading > loading done
fonts > otf loading > saving '/usr/local/opt/lmtx/tex/texmf/fonts/opentype/public/lm/lmroman12-regular.otf' in cache
system > lua > compiling '/home/vladimir/.cache/lmtx/luatex-cache/context/5fe67e0bfe781ce0dde776fb1556f32e/fonts/otl/lmroman12-regular.tma' into '/home/vladimir/.cache/lmtx/luatex-cache/context/5fe67e0bfe781ce0dde776fb1556f32e/fonts/otl/lmroman12-regular.tmd'
system > lua > dumping '/home/vladimir/.cache/lmtx/luatex-cache/context/5fe67e0bfe781ce0dde776fb1556f32e/fonts/otl/lmroman12-regular.tma' into '/home/vladimir/.cache/lmtx/luatex-cache/context/5fe67e0bfe781ce0dde776fb1556f32e/fonts/otl/lmroman12-regular.tmd' stripped
fonts > otf loading > loading, optimizing, packing and caching time 0.060
mtx-context | fatal error: return code: 136
--------------------------- 8< -----------------------------
I don't see any core dump but on other examples being fine with
context I see this "fatal error" but with the same return code.
Or I missed something? Is luatex-cache (as in log above) a cache?
P.S. I have the following *tex* env. variables set in the session:
--------------------------- 8< -----------------------------
$ env | grep -i tex
PWD=/home/vladimir/works/tex/context/examples
TEXMFCACHE=/home/vladimir/.cache/lmtx
PATH=/usr/local/opt/lmtx/tex/texmf-linux-64/bin:/home/vladimir/bin:/usr/local/opt/texlive/2019/bin/x86_64-linux:/usr/bin:/usr/bin/core_perl:/usr/bin/vendor_perl:/usr/local/bin:/bin
OSFONTDIR=/usr/share/fonts;/usr/local/share/fonts;/usr/local/opt/texlive/2019/texmf-dist/fonts/truetype;/usr/local/opt/texlive/2019/texmf-dist/fonts/opentype
OLDPWD=/home/vladimir/works/tex/context
--------------------------- 8< -----------------------------
---
WBR, Vladimir Lomov
--
The absence of labels [in ECL] is probably a good thing.
-- T. Cheatham
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
[-- Attachment #2: 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
___________________________________________________________________________________
next prev parent reply other threads:[~2019-11-29 11:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-29 6:32 Floris van Manen
2019-11-29 9:34 ` Hans Hagen
2019-11-29 11:39 ` Vladimir Lomov [this message]
2019-11-29 12:20 ` Vladimir Lomov
2019-11-29 14:16 ` Floris van Manen
[not found] ` <ec848ffb-9228-a121-7e68-0d421c22b5e6@klankschap.nl>
2019-11-29 20:47 ` Hans Hagen
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=20191129113914.GA869@smoon.bkoty.ru \
--to=lomov.vl@yandex.ru \
--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).