> Am 2010-10-08 um 09:59 schrieb Florian Wobbe:
> 
>>> Thank you, but the problem is most probably something in my server setup 
>>> that doesn't fit something in LuaTeX.
>>> As I mentioned: I got no problems calling TeX directly, just from the 
>>> server process.
>> 
>> All right. I have one more suggestion. If you don't want to dive into 
>> debugging via gdb you should try another attempt at strace. Previously you 
>> posted a tracedump of context. But it only shows context (the shell script) 
>> waiting and nothing related to luatex. You may want to make strace follow 
>> forks (-f).
> 
> 
> Sorry, I've no experience using strace.

Some things are explained here: http://blog.ksplice.com/tag/unix/

> Here we are:
> 
> This is how my process tree looked:
> 14025 ?        Sl     0:01      |   \_ /var/www/xxx/bin/python 
> /var/www/xxx/.../manage.py runfcgi  ...
> 14116 ?        S      0:00      |       \_ /bin/sh -c set >> _context.log && 
> strace -f context --batchmode --once hello >> _context.log
> 14117 ?        S      0:00      |           \_ strace -f context --batchmode 
> --once hello
> 14118 ?        T      0:00      |               \_ /bin/sh 
> /var/opt/context/tex/texmf-linux-64/bin/context --batchmode --once hello
> 14119 ?        R      0:11      |                   \_ texlua 
> /var/opt/context/tex/texmf-linux-64/bin/mtxrun --script context --batchmode 
> --once hello
> 
> The logfile was empty, texlua seemed to hang. I killed 14119 and got:
> [...]
> [pid 14119] brk(0xaa3c000)              = 0xaa3c000
> [pid 14119] brk(0xaa5f000)              = 0xaa5f000
> [pid 14119] brk(0xaa82000)              = 0xaa82000
> [pid 14119] brk(0xaaa3000)              = 0xaaa3000
> [pid 14119] uname({sys="Linux", node="aine.fiee.net", ...}) = 0

This output looks quite messy because it is composed of the mixed output for 
five processes. I don't suspect the fault in luatex executable itself, however, 
mtxrun calls uname -m in a subshell and my guess is that it hangs there. Have 
you tried calling uname alone from your script? Next you could do

 strace -ff -o ctxtrace mtxrun --script context --batchmode --once hello

This gives you hopefully four ctxtrace.<pid> files. Then do (for each pid)

 strace -p <pid>

before killing luatex and see where it hangs. Interrupt and kill your luatex 
and have a look at the ctxtrace.* files.

Florian

___________________________________________________________________________________
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
___________________________________________________________________________________

Reply via email to