It used to be that on the rare occasions that Zope hung, I could
use the recipe at
to diagnose the problem (usually my own code was at fault). But, what
does it mean when I get nothing at all from "info threads" in gdb?  

I get this on two different systems:

system A:
zope 2.7.7
gdb 5.2-2

system B:
python 2.3.4
zope 2.7.3
gdb 5.2-2

Lately this seems to happen regardless of whether
Zope is responsive or not. e.g.:

$ cat
$ cat /zope/ZopeInstanceHome/var/ 
$ sudo gdb python2.3
GNU gdb Red Hat Linux (5.2-2)
Copyright 2002 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you
are welcome to change it and/or distribute copies of it under certain
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for
This GDB was configured as "i386-redhat-linux"...
(gdb) attach 24161
Attaching to program: /usr/local/bin/python2.3, process 24161
Reading symbols from /lib/

(snip copious output)

Reading symbols from
Loaded symbols for /usr/local/lib/python2.3/lib-dynload/
0x080775af in PyDict_GetItem (op=0x44d16934, key=0x401ae020)
    at Objects/dictobject.c:498
498             return (mp->ma_lookup)(mp, key, hash)->me_value;
(gdb) info threads

That's it, nothing.  It used to work for me.
Any clues?


Paul Winkler
Zope maillist  -
**   No cross posts or HTML encoding!  **
(Related lists - )

Reply via email to