Debugging reportbug.
I've been hit by #610348 for some time now. I didn't comment on the bug report because I failed to find useful information to add there.
I've tried several things:
- using strace, one can find that
reportbug
freeze waiting for a returning futex. - using ltrace, the freeze happen while calling
sem_wait
. It also happen sooner: the gui is not opened yet. - using gdb I can sees that the
sem_wait
call have been made fromPyThread_acquire_lock
, but this seem only logical.
All this together give me no useful information. Further testing show that:
- the freeze don't always happen at the same time, and using python2.5 seem to make it happen latter.
- Trying to run it in another environment (say gnome) or with another user do not solve this for me.
- The problem don't exist in a brand new chroot, prooving it's a configuration problem. But which one?
- using meld I've tried to find
significant difference between the two
/etc
, but found nothing that explain the problem.
I have no idea on what to do next to find where is the problem...
I'd probably look in the direction of toolkit bindings being used in ways they are not specified to be used. (Something like a bad interaction between callbacks needing a lock and something else holding it.) Or you could try to emit something on all locking.