From: "Thomas A. Schmitz via ntg-context" <ntg-context@ntg.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Cc: "Thomas A. Schmitz" <thomas.schmitz@uni-bonn.de>
Subject: Heisenbug in current?
Date: Wed, 23 Nov 2022 23:01:30 +0100 [thread overview]
Message-ID: <74314ef5-0e5e-9277-6569-e67d6b4504ab@uni-bonn.de> (raw)
Hi all,
I'm very hesitant to report this because I can't reproduce it
consistently: some of my files don't compile with bizarre font errors,
sometimes. At first I thought it may be a hardware problem on my laptop,
but I've seen more or less the same error on 3 different computers now,
intermittently. The offending call is always similar:
fonts > otf loading > loading
'/mnt/shared/lmtx/tex/texmf/fonts/data/public/dejavu/DejaVuSansMono.ttf',
hash 'dejavusansmono'
otf reader > fatal error in file
'/mnt/shared/lmtx/tex/texmf/fonts/data/public/dejavu/DejaVuSansMono.ttf':
...e0dde776fb1556f32e/formats/luametatex/font-otr-macro.lua:1040:
attempt to call a nil value (field 'to16dot16')
It concerns several fonts, both my own and (as here) from the
installation, and the first error is always this "field 'to16dot16.'"
Has anybody else seen this? Do the developers have any idea what this
could be? Has there been a change in the code concerning this field?
Sorry for being so vague, but I'm pulling my hair because this error
crops up totally at random, AFAICS.
All best
Thomas
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context
webpage : https://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : https://contextgarden.net
___________________________________________________________________________________
next reply other threads:[~2022-11-23 22:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-23 22:01 Thomas A. Schmitz via ntg-context [this message]
2022-11-23 22:25 ` Hans Hagen via ntg-context
2022-11-23 22:40 ` Thomas A. Schmitz via ntg-context
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=74314ef5-0e5e-9277-6569-e67d6b4504ab@uni-bonn.de \
--to=ntg-context@ntg.nl \
--cc=thomas.schmitz@uni-bonn.de \
/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).