From: luigi scarso <luigi.scarso@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: [luatex] Itemize without page break
Date: Tue, 20 Mar 2012 22:41:34 +0100 [thread overview]
Message-ID: <CAG5iGsAZcsFkXrE5hzTEXtundZX3kYt5i=88Csz+Cn5Zd2YQcA@mail.gmail.com> (raw)
In-Reply-To: <1332278680.3358.325.camel@kip-laptop>
On Tue, Mar 20, 2012 at 10:24 PM, Kip Warner <kip@thevertigo.com> wrote:
> On Tue, 2012-03-20 at 21:39 +0100, luigi scarso wrote:
>> When TeX says
>> ! TeX capacity exceeded, sorry [token memory size=<...>]
>> it is its graceful way to exit from an irreversible situation.
>> It can be caused by luatex or ConTeXt mkiv
>> but it's *not* a segmentation fault, as you said early:
>> >Actually highly probably, since the seg fault is raised in luatex and
>> >not context. Even if context is feeding it malformed input, luatex
>> >should not ever crash.
>> Only luatex can do a segmentation fault -- of course due a tex macro
>> /lua function possibly called from ConTeXt.
>> What happen for me (linux ubuntu 10lts 32bit) and Hans (windows (7
>> professional 64bit ?) ) is a "TeX capacity exceeded," , not a seg.
>> fault, and sometime happen if one calls a macro in a wrong way.
>> So, do you have a segmentation fault or a TeX capacity exceeded on you
>> linux 64bit box ?
>
> As I said earlier, I get a segmentation fault if I leave it to run, but
> I always have to kill it before it takes down the entire operating
> system with it (apparently this is normal). I don't get the TeX capacity
> exceeded error message, as you saw from my earlier console output.
Ok, this is not normal and I suspect that it's linux 64bit issue --
can be bug of luatex then.
Can anyone confirm that on linux 64bit the following
\starttext
\startitemize[before=\startlinecorrection,after=\stoplinecorrection][]
\item foo
\stopitemize
\stoptext
gives a segmentation fault ?
--
luigi
___________________________________________________________________________________
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-03-20 21:41 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-17 1:47 Kip Warner
2012-03-17 9:21 ` luigi scarso
2012-03-17 10:21 ` Wolfgang Schuster
2012-03-18 23:25 ` Kip Warner
2012-03-18 23:29 ` Kip Warner
2012-03-19 8:17 ` Wolfgang Schuster
2012-03-20 1:04 ` Kip Warner
2012-03-20 5:22 ` Wolfgang Schuster
2012-03-20 5:31 ` Kip Warner
2012-03-20 5:46 ` Wolfgang Schuster
2012-03-20 5:49 ` Kip Warner
2012-03-20 7:21 ` [luatex] " Patrick Gundlach
2012-03-20 15:02 ` Khaled Hosny
2012-03-20 8:17 ` Hans Hagen
2012-03-20 10:05 ` luigi scarso
2012-03-20 18:50 ` Kip Warner
2012-03-20 14:57 ` [luatex] " Khaled Hosny
2012-03-20 18:59 ` Kip Warner
2012-03-20 19:26 ` Hans Hagen
2012-03-20 19:59 ` Kip Warner
2012-03-20 20:39 ` luigi scarso
2012-03-20 21:24 ` Kip Warner
2012-03-20 21:41 ` luigi scarso [this message]
2012-03-22 1:50 ` Kip Warner
2012-03-20 20:44 ` Hans Hagen
2012-03-20 21:26 ` Kip Warner
2012-03-20 22:18 ` Kip Warner
2012-03-20 22:22 ` Aditya Mahajan
2012-03-22 2:01 ` Kip Warner
2012-03-22 10:38 ` Mojca Miklavec
2012-03-22 10:48 ` Hans Hagen
2012-03-22 10:48 ` Hans Hagen
2012-03-22 11:21 ` Philipp Gesang
2012-03-22 11:58 ` Philipp Gesang
2012-03-22 22:47 ` Kip Warner
2012-03-22 22:46 ` Kip Warner
2012-03-22 22:40 ` Kip Warner
2012-03-22 12:05 ` luigi scarso
2012-03-22 16:38 ` luigi scarso
2012-03-19 21:49 ` Hans Hagen
2012-03-20 0:43 ` Kip Warner
2012-03-20 8:11 ` Hans Hagen
2012-03-18 23:33 ` luigi scarso
2012-03-19 21:50 ` Hans Hagen
2012-03-20 0:41 ` Kip Warner
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='CAG5iGsAZcsFkXrE5hzTEXtundZX3kYt5i=88Csz+Cn5Zd2YQcA@mail.gmail.com' \
--to=luigi.scarso@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).