From: Aditya Mahajan <adityam@umich.edu>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Luatex crash on \endinput \end
Date: Wed, 16 May 2012 19:06:41 -0400 (EDT) [thread overview]
Message-ID: <alpine.LNX.2.02.1205161903450.24041@qrpragenyvmrq> (raw)
In-Reply-To: <CAG5iGsAzF2Y08Ln01Hqs_OO6fRTyF+1xrRUaZ0zs7o8QybEgDg@mail.gmail.com>
[-- Attachment #1: Type: TEXT/PLAIN, Size: 4293 bytes --]
On Wed, 16 May 2012, luigi scarso wrote:
> On Wed, May 16, 2012 at 6:12 PM, Aditya Mahajan <adityam@umich.edu> wrote:
>> Hi,
>>
>> The following causes luatex to crash (it is harmless, but still...)
>>
>> echo '\\endinput \\end' | context --pipe
>>
>> gives:
>>
>> *** glibc detected *** luatex: double free or corruption (fasttop):
>> 0x0aef00e8 ***
>> ======= Backtrace: =========
>> /lib/libc.so.6(+0x725f2)[0xb75f05f2]
>> luatex(luacstring_close+0x7b)[0x810153b]
>> luatex(end_file_reading+0xd8)[0x80b0858]
>> luatex[0x80d88e7]
>> luatex[0x80d75d4]
>> luatex(get_next+0x5d)[0x80d8cfd]
>> luatex(get_x_token+0x15)[0x80acc35]
>> luatex(main_control+0x48)[0x80b4328]
>> luatex(main_body+0x21d)[0x80b1ebd]
>> luatex(main+0x20)[0x8090d40]
>> /lib/libc.so.6(__libc_start_main+0xf3)[0xb7597483]
>> ======= Memory map: ========
>> 08048000-08464000 r-xp 00000000 08:03 810362
>> /opt/context-minimals/texmf-linux/bin/luatex
>> 08464000-084d2000 rw-p 0041c000 08:03 810362
>> /opt/context-minimals/texmf-linux/bin/luatex
>> 084d2000-0878d000 rw-p 00000000 00:00 0
>> 09838000-0af96000 rw-p 00000000 00:00 0 [heap]
>> b5554000-b5ae4000 rw-p 00000000 00:00 0
>> b5b46000-b5c27000 rw-p 00000000 00:00 0
>> b5e45000-b6006000 rw-p 00000000 00:00 0
>> b60a4000-b60c0000 r-xp 00000000 08:03 1006974 /usr/lib/libgcc_s.so.1
>> b60c0000-b60c1000 rw-p 0001b000 08:03 1006974 /usr/lib/libgcc_s.so.1
>> b60e7000-b72de000 rw-p 00000000 00:00 0
>> b72df000-b73b7000 rw-p 00000000 00:00 0
>> b73b7000-b757c000 r--p 00000000 08:03 1856687 /usr/lib/locale/locale-archive
>> b757c000-b757e000 rw-p 00000000 00:00 0
>> b757e000-b7719000 r-xp 00000000 08:03 1479914 /lib/libc-2.15.so
>> b7719000-b771b000 r--p 0019b000 08:03 1479914 /lib/libc-2.15.so
>> b771b000-b771c000 rw-p 0019d000 08:03 1479914 /lib/libc-2.15.so
>> b771c000-b771f000 rw-p 00000000 00:00 0
>> b771f000-b7749000 r-xp 00000000 08:03 1479882 /lib/libm-2.15.so
>> b7749000-b774a000 r--p 00029000 08:03 1479882 /lib/libm-2.15.so
>> b774a000-b774b000 rw-p 0002a000 08:03 1479882 /lib/libm-2.15.so
>> b774b000-b774e000 r-xp 00000000 08:03 1479881 /lib/libdl-2.15.so
>> b774e000-b774f000 r--p 00002000 08:03 1479881 /lib/libdl-2.15.so
>> b774f000-b7750000 rw-p 00003000 08:03 1479881 /lib/libdl-2.15.so
>> b7773000-b7777000 rw-p 00000000 00:00 0
>> b7777000-b7778000 r-xp 00000000 00:00 0 [vdso]
>> b7778000-b7798000 r-xp 00000000 08:03 1479958 /lib/ld-2.15.so
>> b7798000-b7799000 r--p 0001f000 08:03 1479958 /lib/ld-2.15.so
>> b7799000-b779a000 rw-p 00020000 08:03 1479958 /lib/ld-2.15.so
>> bfeeb000-bff0d000 rw-p 00000000 00:00 0 [stack]
>>
>> Aditya
>
>
> # echo '\\endinput \\end' | context --pipe
>
> mtx-context | entering scrollmode, end job with \endThis is
> LuaTeX, Version beta-0.70.1-2011051923 (rev 4277)
> \write18 enabled.
>
> ConTeXt ver: 2012.05.08 23:00 MKIV fmt: 2012.5.9 int: english/english
>
> system > cont-new.mkiv loaded
> (/opt/luatex/standalone-bassenge/tex/texmf-context/tex/context/base/cont-new.mkiv
> system > beware: some patches loaded from cont-new.mkiv
> )
> system > no texput.top
> fonts > latin modern fonts are not preloaded
> languages > language en is active
>
> *
> *
> ! Emergency stop.
>
> system > tex > error on line 0 in file : Emergency stop ...
>
> <empty file>
>
> <*> \\endinput \\end
>
> ! ==> Fatal error occurred, no output PDF file produced!
> system | total runtime: 1.127
> root@luigicasa-laptop:/opt/luatex/standalone-bassenge/tex/texmf-project/math#
> luatex -version
> This is LuaTeX, Version beta-0.70.1-2011051923 (rev 4277)
>
> ubuntu 10.04 lts 32bit
Hmm... I am using (I also tested on 2012.04.26 22:27 MKIV)
mtx-context | entering scrollmode, end job with \endThis is LuaTeX,
Version beta-0.70.1-2011051923 (rev 4277)
\write18 enabled.
ConTeXt ver: 2012.05.14 16:00 MKIV fmt: 2012.5.16 int: english/english
on arch linux 32bit:
$ uname -a
Linux ... 3.3.3-1-ARCH #1 SMP PREEMPT Mon Apr 23 09:33:32 UTC
2012 i686 Intel(R) Core(TM) i7-2600 CPU @ 3.40GHz GenuineIntel GNU/Linux
Aditya
[-- Attachment #2: Type: text/plain, Size: 485 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://tex.aanhet.net
archive : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2012-05-16 23:06 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-16 16:12 Aditya Mahajan
2012-05-16 16:42 ` luigi scarso
2012-05-16 23:06 ` Aditya Mahajan [this message]
2012-05-17 12:24 ` luigi scarso
2012-05-17 13:44 ` Taco Hoekwater
2012-05-17 14:30 ` Aditya Mahajan
2012-05-17 23:17 ` Vladimir Lomov
2012-05-18 8:58 ` Taco Hoekwater
2012-05-18 9:06 ` luigi scarso
2012-05-18 9:36 ` Aditya Mahajan
2012-05-18 9:44 ` Hans Hagen
2012-05-18 10:34 ` Taco Hoekwater
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=alpine.LNX.2.02.1205161903450.24041@qrpragenyvmrq \
--to=adityam@umich.edu \
--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).