14
votes

Is there a way to see which signals are fired, and if there is a slot connected to them? Ideally, we'd like to see all signals, not just those of a particular class or method; e.g. QSignalSpy only allows us to track specific signals of specific instances.

In our application, we've seen performance problems because of a signal being emitted twice from different components. In the end, it turned out that there was a second instance of a class that should have only been there once. Knowing which signals are emitted exactly helps in debugging this.

Signals are called via QMetaObject::invoke*, I was hoping to find something there to hook into, but I found nothing obvious.

2
If you want to have just one instance of the class, why didn't you use the singleton pattern to control number of objects?Afshin

2 Answers

5
votes

(disclaimer, I work for KDAB) : KDAB's GammaRay tool can show you objects and connections at runtime, without requiring any source changes. It inspects the meta-object tables and does some code-injection hooks to make this work.

1
votes

QSignalSpy could help you.

From docs,

The QSignalSpy class enables introspection of signal emission.QSignalSpy can connect to any signal of any object and records its emission.

The docs has examples too..