From: Hans Hagen <j.hagen@xs4all.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Lua related change in LuaMetaTeX?
Date: Wed, 29 Jul 2020 11:07:49 +0200 [thread overview]
Message-ID: <b75dafe2-63df-4ecd-599d-579abf13b8b5@xs4all.nl> (raw)
In-Reply-To: <20200729042203.3g4fieqthl5klus3@yoga>
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
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl
-----------------------------------------------------------------
___________________________________________________________________________________
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:[~2020-07-29 9:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-29 4:22 Marcel Fabian Krüger
2020-07-29 9:07 ` Hans Hagen [this message]
2020-07-29 16:11 ` Marcel Fabian Krüger
2020-07-29 16:36 ` Hans Hagen
2020-07-29 17:48 ` Marcel Fabian Krüger
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=b75dafe2-63df-4ecd-599d-579abf13b8b5@xs4all.nl \
--to=j.hagen@xs4all.nl \
--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).