Implement an option to disable generation of callback calls for which registration or/and deregistration is unknown
Recent results showed that heuristical registration and deregistration of callbacks immediately after module initialization and before module exit correspondingly lead to many false positives. Thus, it is proposed to implement an option to disable such heuristical addiction of registration and deregistration.
#1 Updated by Evgeny Novikov about 1 year ago
- Priority changed from High to Urgent
- Target version set to 2.0
I think that this option is very easy to implement while it will eliminate quite many false alarms - calling callbacks with unknown registration/deregistration should be switched off by default. Indeed it seems I never saw a bug detected by such the registration/deregistration pattern.