From: Henri Menke <henrimenke@gmail.com>
To: ntg-context@ntg.nl
Subject: Re: context (lmtx) segfaults on x86_64 linux
Date: Wed, 11 Sep 2019 11:19:57 +1200 [thread overview]
Message-ID: <4e89aa04-075f-cb66-e94b-51c576304fce@gmail.com> (raw)
In-Reply-To: <nycvar.YAK.7.76.1909101149440.1621@nqv-guvaxcnq>
[-- Attachment #1.1.1: Type: text/plain, Size: 1673 bytes --]
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.
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.
Cheers, Henri
>
> Aditya
> ___________________________________________________________________________________
> 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
> ___________________________________________________________________________________
>
[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 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-09-10 23:19 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-10 14:11 Vladimir Lomov
2019-09-10 15:18 ` Hans Hagen
2019-09-10 15:50 ` Aditya Mahajan
2019-09-10 23:19 ` Henri Menke [this message]
2019-09-11 1:41 ` Vladimir Lomov
2019-09-11 6:39 ` Hans Hagen
2019-09-11 8:14 ` Vladimir Lomov
2019-09-11 8:38 ` Hans Hagen
2019-09-11 8:51 ` Vladimir Lomov
2019-09-11 8:54 ` Hans Hagen
2019-09-11 9:02 ` Vladimir Lomov
2019-09-11 9:40 ` Hans Hagen
2019-09-11 7:03 ` Hans Hagen
2019-09-11 1:06 ` Vladimir Lomov
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=4e89aa04-075f-cb66-e94b-51c576304fce@gmail.com \
--to=henrimenke@gmail.com \
--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).