![](https://secure.gravatar.com/avatar/f00b3effe60730dd7e12f6636a29ffc9.jpg?s=120&d=mm&r=g)
Hello, ** Henri Menke [2019-09-11 11:19:57 +1200]:
On 9/11/19 3:50 AM, Aditya Mahajan wrote:
On Tue, 10 Sep 2019, Hans Hagen wrote:
On 9/10/2019 4:11 PM, Vladimir Lomov wrote:
Hello, today I updated lmtx and on simple
$ context --version
I get segfault (in the same time luametatex --version works fine). Running under gdb shows me that the problem might be in one of 'realloc' calls.
The context from Context Suite (mkiv) works fine.
P.S. I tested on two systems, both runs Archlinux x86_64. can you completely wipe the texmf-cache directory and then run
mtxrun --generate context --make
(there is a change in bytecode that gets not automatically noticed that can give that crash)
I had the same issue and completely wiping the texmf-cache fixes it.
@Vladimir: If you are using the luametatex package from AUR, then the texmf-cache is located at $HOME/.cache/luametatex.
No, I don't use the package from AUR, I simply do /usr/local/opt/lmtx $ sudo ./install.sh but I explicitly set TEXMFCACHE=$HOME/.cache/lmtx (for context suite I set it to $HOME/.cache/context-suite).
I'm receiving the super helpful error message:
! error (lua): function call: no
Maybe some sort of cache versioning is in order to at least give a better error.
It didn't occured to me that the problem may be with the cache, it would be helpfull if context/luametatex will give error message, something like "cache version mismatch" and exit.
Cheers, Henri
Aditya
--- WBR, Vladimir Lomov -- Sometimes I live in the country, And sometimes I live in town. And sometimes I have a great notion, To jump in the river and drown.