How do I debug weird memory management issues in Xcode/Objective-C? -


I'm new to Objective-C and my memory management skills are not great. However, I still have a problem And now I have big problems.

I have gone from zero crash to crash at random points, or I have an unknown selector error at any console output or random type ( - [NSCFSet isSameSsStop:]: Unknown selector - I also do not use any set and I have definitely not called my custom problem on any set.) Looking at the randomness and errors, it seems like a memory thing to me, though I'm not completely sure.

How would I go about debugging it? The debugger assumes that you where is your problem ... and I am only everywhere

Some explanations on the solution suggestion "Run with competent zombie identity":

  • NSGOWE's executables' arguments screen But set to Yes.
  • Create and then choose Run with Display Tools> Object Allocation, which will start Instruments.
  • Click the "i" button to select the object allocation zombie in the instr and select to maintain it.
  • Run again and click around in your app, it tells you that when you hit a zombie!

Thanks for the help!

There is a classic over-release bug on your hands somewhere, you are issuing an instance of that class Which implements isSameAsStop and it happens that after the original charge is canceled, an NSSet example is allocated in the same place.

The first step is to determine your problem in order to "construct and analyze" your code, which determines the stable analyzer.

The next step is to run with zombie identification enabled.


Comments