Mark Dickinson added the comment: One thing that looks a bit odd to my eyes is the different values for `lock` in the PyThread_acquire_lock calls (see below). All of threads 2-5 should be waiting on the GIL, so I'd expect to see the same value for `lock` in all those calls. Instead, threads 2 and 5 seem to be waiting on the same lock, but threads 3 and 4 seem to have their own lock. But I don't know this code well enough to know whether it's supposed to be this way.
Thread 5 (Thread 0x1903 of process 14075): #2 0x00000001000e7e21 in PyThread_acquire_lock (lock=0xed3ed500, waitflag=<optimized out>) at Python/thread_pthread.h:429 Thread 4 (Thread 0x1803 of process 14075): #2 0x00000001000e7e21 in PyThread_acquire_lock (lock=0xed3ed300, waitflag=<optimized out>) at Python/thread_pthread.h:429 Thread 3 (Thread 0x1703 of process 14075): #2 0x00000001000e7e21 in PyThread_acquire_lock (lock=0xed3ed600, waitflag=<optimized out>) at Python/thread_pthread.h:429 Thread 2 (Thread 0x1603 of process 14075): #2 0x00000001000e7e21 in PyThread_acquire_lock (lock=0xed3ed300, waitflag=<optimized out>) at Python/thread_pthread.h:429 Thread 1 (Thread 0x1503 of process 14075): #2 0x00000001000e7e21 in PyThread_acquire_lock (lock=0x0, waitflag=<optimized out>) at Python/thread_pthread.h:429 ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue26360> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
