Ticket #348 (closed enhancement: fixed)
provide a way to debug framework when it goes to a state where it does not respond to dbus
|Reported by:||lindi||Owned by:||mickey|
This is a wishlist bug about making framework easier to debug.
After some time framework sometimes goes to a state where it does not reply to any dbus calls. However, it is connected to dbus since it can send signals when an incoming call occurs. At present I don't know any good way to investigate the state of the framework process when it has hit this broken state. GDB is able to show instruction traces but I was not able to figure out what is going on there.
Maybe we could have framework listen on some UNIX socket and evaluate any python expressions that are written to this socket? Or maybe there are some GDB macros that could make python debuggable with gdb?