From: Hans Hagen <j.hagen@xs4all.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: context (lmtx) segfaults on x86_64 linux
Date: Wed, 11 Sep 2019 09:03:34 +0200 [thread overview]
Message-ID: <b18f4a47-0ccb-eccc-3f78-8dfac50af78f@xs4all.nl> (raw)
In-Reply-To: <4e89aa04-075f-cb66-e94b-51c576304fce@gmail.com>
On 9/11/2019 1:19 AM, Henri Menke wrote:
> 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
there is not much context to present there as it means that deep down a
bad function token is expanded, something under control of the macro
package, which then has/is messed up
> Maybe some sort of cache versioning is in order to at least give a better error.
for now, adding
\ifdefined\pdfsavepos\else
\let\pdfsavepos \savepos
\let\pdflastxpos\lastxpos
\let\pdflastypos\lastypos
\fi
to cont-new.mkiv seems to work ok
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:[~2019-09-11 7:03 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
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 [this message]
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=b18f4a47-0ccb-eccc-3f78-8dfac50af78f@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).