[NTG-context] Lua related change in LuaMetaTeX?

Hans Hagen j.hagen at xs4all.nl
Wed Jul 29 11:07:49 CEST 2020

On 7/29/2020 6:22 AM, Marcel Fabian Kr├╝ger wrote:
> Hi,
> starting with LuaMetaTeX 2.07.01, a C library I load from Lua started to
> segfault and valgrind indicates that it accesses invalid memory in
> multiple places in the middle of Lua internal functions?!
> The whole thing looks almost like the Lua versions in LuaMetaTeX and in
> the library are incompatible, but both seem to use 5.4.0. So I asked
> myself if there might be changes not reflected by the version number.
> tl;dr: Has the embedded Lua interpreter changed in some non ABI-compatible
> way in LuaMetaTeX 2.07.01? (Especially on Linux, x86-64. I didn't test
> other platforms yet)
there have been a couple of bug fixes after the formal 5.4.0 release but 
afaik not in the virtual machine code (which normally is the most 
sensitive); i used to mark low level changes so that it got signaled (in 
context) but the byte code version info changed late in 5.4 dev so i no 
longer do that now

although i occasionally have run into buglets in 5.4 code - which to me 
is quite natural as it concerns dev / exp versions so one gets what one 
downloads, i.e. one can only blame oneself for using such versions and 
hardly complain - lua is quite stable and reliable (given the massive 
amount of lua code that we use in context) ... so, normally patience - 
read: wait for updates - is the answer


                                           Hans Hagen | PRAGMA ADE
               Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
        tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl

More information about the ntg-context mailing list