Paul Winkler wrote at 2005-8-1 12:12 -0400:
> ...
>But, what
>does it mean when I get nothing at all from "info threads" in gdb?
That "gdb" does not understand the OS structures.
I found that "gdb" has significant problems to understand
"core" files of multithreaded applications and
is easily c
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
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)->m
It used to be that on the rare occasions that Zope hung, I could
use the recipe at http://zopelabs.com/cookbook/1073504990
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:
