Le 16/05/2010 17:10, Elie Roux a écrit : >> This is beyond my capability to debug in my present post-hangover >> state. (Tips on exactly what to do here greatly appreciated, however.) > > For memory leaks and errors, the best way to debug is to use valgrind. > There is a very experimental port to Mac OSX, but I think it would be a > good first start. If you manage to make it run, run it with maximum > verbosity (there are quite a lot of options) on the execution that > causes errors, and send the restults to luatex-dev. Anyway, these errors > seem quite serious :( > Unless I'm seriously mistaken, memory allocation errors are not your (as Lua programmer = texlua user) responsibility, but mean there is a problem in the engine itself.
It would be good to have a small reproducer and send it to the LuaTeX team. Manuel.
