From: "Marcel Fabian Krüger" <tex@2krueger.de>
To: ConTeXt users list <ntg-context@ntg.nl>
Subject: LuaMetaTex dereferences NULL pointer
Date: Tue, 1 Sep 2020 01:40:48 +0200 [thread overview]
Message-ID: <20200831234048.ayn4shjxzfn5tgkd@yoga> (raw)
Hi,
with the latest LuaMetaTeX upload (running on Linux x64),
\normalunexpanded tries to write to address 0 and therefore
segfaults:
\normalunexpanded{abc}
\starttext
\stoptext
ConTeXt fails with
mtx-context | fatal error: return code: 139
The most interesting message from valgrind is
==53200== Invalid write of size 4
==53200== at 0x17113D: ??? (in /home/marcel/lmtx-install/tex/texmf-linux-64/bin/luametatex)
==53200== by 0x151625: ??? (in /home/marcel/lmtx-install/tex/texmf-linux-64/bin/luametatex)
==53200== by 0x151E40: ??? (in /home/marcel/lmtx-install/tex/texmf-linux-64/bin/luametatex)
==53200== by 0x15E1A2: ??? (in /home/marcel/lmtx-install/tex/texmf-linux-64/bin/luametatex)
==53200== by 0x154AA1: ??? (in /home/marcel/lmtx-install/tex/texmf-linux-64/bin/luametatex)
==53200== by 0x122347: ??? (in /home/marcel/lmtx-install/tex/texmf-linux-64/bin/luametatex)
==53200== by 0x4A0C151: (below main) (in /usr/lib/libc-2.32.so)
==53200== Address 0x0 is not stack'd, malloc'd or (recently) free'd
==53200==
==53200==
==53200== Process terminating with default action of signal 11 (SIGSEGV): dumping core
==53200== Access not within mapped region at address 0x0
==53200== at 0x17113D: ??? (in /home/marcel/lmtx-install/tex/texmf-linux-64/bin/luametatex)
==53200== by 0x151625: ??? (in /home/marcel/lmtx-install/tex/texmf-linux-64/bin/luametatex)
==53200== by 0x151E40: ??? (in /home/marcel/lmtx-install/tex/texmf-linux-64/bin/luametatex)
==53200== by 0x15E1A2: ??? (in /home/marcel/lmtx-install/tex/texmf-linux-64/bin/luametatex)
==53200== by 0x154AA1: ??? (in /home/marcel/lmtx-install/tex/texmf-linux-64/bin/luametatex)
==53200== by 0x122347: ??? (in /home/marcel/lmtx-install/tex/texmf-linux-64/bin/luametatex)
==53200== by 0x4A0C151: (below main) (in /usr/lib/libc-2.32.so)
==53200== If you believe this happened as a result of a stack
==53200== overflow in your program's main thread (unlikely but
==53200== possible), you can try to increase the size of the
==53200== main thread stack using the --main-stacksize= flag.
==53200== The main thread stack size used in this run was 8388608.
Best regards,
Marcel
___________________________________________________________________________________
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
___________________________________________________________________________________
reply other threads:[~2020-08-31 23:40 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20200831234048.ayn4shjxzfn5tgkd@yoga \
--to=tex@2krueger.de \
--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).