[Zope] Asking advice on a Zope "stuck" (or: what did I do wrong?)

[Dieter Maurer]

Marco Bizzarri wrote at 2008-8-2 09:33 +0200:
> ....
>I installed DeadlockDebugger, and tried to have a dump from it, but it
>is unable to answer, at leasts it seems to me.
>
>So, I followed the recipe from ZopeLabs:
>
>http://www.zopelabs.com/cookbook/1073504990
>
>and got a traceback from gdb.
>
>info threads gives the following:
>
>* 5 Thread 0xb5b29b90 (LWP 17713)  0xffffe410 in __kernel_vsyscall ()
>  4 Thread 0xb5322b90 (LWP 17714)  0xffffe410 in __kernel_vsyscall ()
>  3 Thread 0xb4b21b90 (LWP 17715)  0xffffe410 in __kernel_vsyscall ()
>  2 Thread 0xb4320b90 (LWP 17716)  0xffffe410 in __kernel_vsyscall ()
>  1 Thread 0xb7d4b8c0 (LWP 17687)  0xffffe410 in __kernel_vsyscall ()
>
>
>I'm including the traceback. As you can see, the last lines tell (for
>all the threads) are:
>
>
>  File "/var/local/zope28/base288/lib/python/Shared/DC/ZRDB/Results.py",
>line 55, in __init__
>    if n != name: aliases.append((n, SQLAlias(name)))

This is unbelievable.

The above Python code should not block (and not cause an infinite
recursion) other than for memory requests.

At C-level, you see to be in a kernel call.
Look closer at the C level tracebacks to find out which kernel
call this is.

You may need to have a Python with debug symbols to get reliable
C level tracebacks.



-- 
Dieter