On Thursday 24 April 2003 02:38 am, Dieter Maurer wrote:

Bakhtiar A Hamid wrote at 2003-4-23 16:21 +0800:

...

....

...

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 do not believe that.

i'm very new at trying out gdb, and i may be wrong most of the time.

"Py_GetProgramFullPath" is only called when Python starts. Thus, it is very unlikely that Python is waiting there.

that's the only thread that's running. i'll try again when this happens and get all necessary threads information

Almost surely, your Python is not compiled for debugging. Then, only global symbos are available for the debugger and tracebacks are likely to be misleading.

If possible, recompile your Python in a way that it contains debugging information and try again.

this is probable. i use python rpm source, and the Makefile has -g (which i think enables debugging?) i may be way over my head this time... thanks for any help

Dieter