Cellular Network Infrastructure » OsmoGSMTester

If there's an (un)expected issue while doing some stuff in the context of a callback function called from a dbus signal coming from glib mainloop and we raise an Exception, we can see the Exception being printed on the stdout but the test is not stopping at that moment, it rather stops after the timeout in wait() at the end.

It would be nice for osmo-gsm-tester to stop everything no matter where the exception comes from. My guess is that the exception is being filtered consciously or unconsciously at some point inside pydbus or glib.

I'd advise modifying some signal callback code to print a backtrace and see the whole code path and then go look over the different frames where is the callback stopped and discarded.