![](https://secure.gravatar.com/avatar/386a116d129cdc597f2bb6210bbaff7a.jpg?s=120&d=mm&r=g)
On Tue, Mar 20, 2012 at 10:24 PM, Kip Warner
On Tue, 2012-03-20 at 21:39 +0100, luigi scarso wrote:
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
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: 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