[ZODB-Dev] ZEO non-communication problem

[Jeremy Hylton]

On Thu, 2003-09-11 at 10:34, Christian Reis wrote:
> Basically, just gdb <pid>, and then do a "where"; it should report the
> (C) call stack. It isn't directly relatable to Python, but it will give
> you the general idea of what it's doing (hung on an unfinished read,
> sleeping, select()ing, etc).

You'll need to navigate among threads if you're debugging zope.  IIRC,
you first type info threads, which will list each thread and what
function it is currently executing.  Then the "thread N" command will
switch to a thread so you can run "where" on its stack.

Again, IIRC, a thread involved that is importing will have C functions
like load_module().

Jeremy