Here is some code to test figures and .fig files to verify the reasonableness of callbacks. All kinds of callbacks are examined and a number of different conditions are potentially reported.
You can use
verifyfig('NameOfFig')
verifyfig()
verifyfig(figure(17))
and there is an optional second argument for excluding some kinds of object types such as uimenu
Sample output:
>> verifyfig('REPORT1')
Callback problems detected
-> in type "uicontrol" object with id 358.0018310546875 Tag "edit1"
--> in type "figure" object with id 532.000244140625 Tag "figure1"
Suspicious callback "Callback" because anonymous function refers to unfound routine "edit1_Callback"
Suspicious callback "CreateFcn" because anonymous function refers to unfound routine "edit1_CreateFcn"
Note: it is common for GUIDE callbacks to not be found. This version of the code is not able to look inside the .m file corresponding to a .fig file in order to determine whether the routines are there. You will need to look over the outputs carefully as the ones you are looking for will be hidden there. On the other hand if you already know the names from the object browser then this tool will help you to track down where the reference to the object is.
There are some enhancements possible to this code, but I just wrote it to answer this Question.
