[Zope] When "Debug Spinning Zope" doesn't work

[Paul Winkler]

On Mon, Aug 01, 2005 at 07:09:03PM +0200, Maciej Wisniowski wrote:
> 
> >Reading symbols from
> >/usr/local/lib/python2.3/lib-dynload/itertools.so...done.
> >Loaded symbols for /usr/local/lib/python2.3/lib-dynload/itertools.so
> >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
> >{gdb)
> >
> >
> >That's it, nothing.  It used to work for me.
> >Any clues?
> >
> Hi!
> 
> Have you tried DeadlockDebugger product?
> Maybe it will tell you what is happening. So far it is working
> perfectly for me.

Good idea, thanks! Will do.

Some googling suggests that "info threads" returns nothing
when gdb is run on a system that doesn't support threads.
But that's absurd in this case.
 
-- 

Paul Winkler
http://www.slinkp.com