I am wondering if there is a tool for static analysis of SIGNAL-SLOT connections in source code. When using Visual Studio to run an app in debug mode, Qt will report when connect() is called with non-existent SIGNAL or SLOT methods. In general, however, these message are output only when the connect() code is executed, so unless you exercise all parts of the UI, you may not see all of the incomplete connections in the code. When making changes to code that involve renaming signals, slots, or changes to their signatures, it is often easy to miss something that needs to be fixed after the change.

Is there a tool that will statically analyze source code and identify these dangling connections?

I am aware of Conan, but this is a run-time analyzer.