Subject: Re: [Zope] zope2.6.1 debugging
From: Chris Withers <[email-masked]>
To: Bakhtiar A Hamid <[email-masked]>
Date: Wed, 23 Apr 2003 09:22:03 +0100

You may wish to try on [email-masked] for gurus skilled enough to unentangle 
this...

Bakhtiar A Hamid wrote:
> hi
> previously, i reported that my zope / zeo clients hangs.  following the howto 
> by evan, i managed to get these when i attach to the 2nd zope pid
> 
> --
> Loaded symbols for 
> /usr/local/Zope-2.6-cvs/lib/python/Products/PluginIndexes/TextIndex/Splitter/ZopeSplitter/ZopeSplitter.so
> 0x0806fb42 in Py_GetProgramFullPath () at eval.c:41
> 41      eval.c: No such file or directory.
>         in eval.c
> 
> and on another zope instance, i have this
> 
> Loaded symbols for 
> /usr/local/Zope-2.6-cvs/lib/python/Products/PluginIndexes/TextIndex/Splitter/ZopeSplitter/ZopeSplitter.so
> 0x4008caa5 in __sigsuspend (set=0xbffff0a0) at 
> ../sysdeps/unix/sysv/linux/sigsuspend.c:45
> 45      ../sysdeps/unix/sysv/linux/sigsuspend.c: No such file or directory.
>         in ../sysdeps/unix/sysv/linux/sigsuspend.c
> 
> --
> all other symbols loaded ok, but not that particular one.  and further, when i 
> looked at the particular thread
> 
> (gdb) info threads
> [New Thread 2050 (LWP 22622)]
> [New Thread 3075 (LWP 22623)]
> [New Thread 4100 (LWP 22624)]
> [New Thread 5125 (LWP 22625)]
>   6 Thread 5125 (LWP 22625)  0x4008caa5 in __sigsuspend (set=0x42d7bc6c) at 
> ../sysdeps/unix/sysv/linux/sigsuspend.c:45
>   5 Thread 4100 (LWP 22624)  0x4008caa5 in __sigsuspend (set=0x4257ba4c) at 
> ../sysdeps/unix/sysv/linux/sigsuspend.c:45
>   4 Thread 3075 (LWP 22623)  0x4008caa5 in __sigsuspend (set=0x41d7aefc) at 
> ../sysdeps/unix/sysv/linux/sigsuspend.c:45
>   3 Thread 2050 (LWP 22622)  0x4008caa5 in __sigsuspend (set=0x4157c15c) at 
> ../sysdeps/unix/sysv/linux/sigsuspend.c:45
>   2 Thread 2049 (LWP 22595)  0x401439f7 in __poll (fds=0x8b6e61c, nfds=1, 
> timeout=2000)
>     at ../sysdeps/unix/sysv/linux/poll.c:63
>   1 Thread 1024 (LWP 22594)  0x0806fb42 in Py_GetProgramFullPath () at 
> eval.c:41
> 
> and in the many instances i looked, the running thread that seemed to hang 
> zope is the one with Py_GetProgramFullPath() 
> 
> i have no real experience with gdb, and i can never get the traceback as 
> suggested by evan's howto. but this is the data that i got.
> 
> any help appreciated
> 
> thanks
> 
> 
> _______________________________________________
> Zope maillist  -  [email-masked]
> http://mail.zope.org/mailman/listinfo/zope
> **   No cross posts or HTML encoding!  **
> (Related lists - 
>  http://mail.zope.org/mailman/listinfo/zope-announce
>  http://mail.zope.org/mailman/listinfo/zope-dev )
> 
>