On Mon, 2014-08-04 at 14:52 +0200, Thomas Woerner wrote:
> Any ideas on how to debug?
> The hanged process on gdb seems to block at:
> #0 0x00007f1dd5a76df0 in __poll_nocancel () from /lib64/libc.so.6
> #1 0x00007f1dcb19d780 in socket_do_iteration ()
> from /lib64/libdbus-1.so.3
> #2 0x00007f1dcb19c5ff in _dbus_transport_do_iteration ()
> from /lib64/libdbus-1.so.3
> #3 0x00007f1dcb185d7c in _dbus_connection_do_iteration_unlocked ()
> from /lib64/libdbus-1.so.3
> #4 0x00007f1dcb18687c in _dbus_connection_block_pending_call ()
> from /lib64/libdbus-1.so.3
> #5 0x00007f1dcb186d3a in dbus_connection_send_with_reply_and_block ()
> from /lib64/libdbus-1.so.3
> #6 0x00007f1dcb3ca0df in Connection_send_message_with_reply_and_block
> ()
> from /usr/lib64/python2.7/site-packages/_dbus_bindings.so
> #7 0x00007f1dd6751b94 in PyEval_EvalFrameEx ()
> from /lib64/libpython2.7.so.1.0
> #8 0x00007f1dd67531ad in PyEval_EvalCodeEx ()
> from /lib64/libpython2.7.so.1.0
I have not seen this error before.
Problem solved. It was the inherited signal mask from the executing
process that caused the issue.
regards,
Nikos