My app contains several singletons (following from this tutorial). I’ve noticed however, when the app crashes because of a singleton, it becomes nearly impossible to figure out where it came from. The app breakpoints at the main function giving an EXEC_BAD_ACCESS even though the problem lies in one of the Singleton objects. Is there a guide to how would I debug my singleton objects if they were problematic?
My app contains several singletons (following from this tutorial ). I’ve noticed however, when
Share
I scanned the article, and while it had some good ideas it also had some bad advice, and it should not be taken as gospel.
And, as others have suggested, if you have a lot of singleton objects it may mean that you’re simply keeping too much state global/persistent. Normally only one or two of your own should be needed (in addition to those that other “packages” of one sort or another may implement).
As to debugging singletons, I don’t understand why you say it’s hard — no worse than anything else, for the most part. If you’re getting EXEC_BAD_ACCESS it’s because you’ve got some sort of addressing bug, and that’s nothing specific to singleton schemes (unless you’re using a very bad one).
Macros make debugging difficult because the lines of code they incorporate can’t have breakpoints put in them. Deep six macros, if nothing else. In particular, the
SYNTHESIZE_SINGLETON_FOR_CLASSmacro from the article is interfering with debugging. Replace the call to this macro function with the code it generates for your singleton class.