objective-c - Tencent bugly locates the crash code in the main function, is there any solution?

Question

The Tencent bugly used by the APP monitors online bugs, but sometimes the crash report displays the crash location in the main function, as follows:

Type belongs to this:

I believe that students who use bugly have encountered it, so how do you deal with this kind of crash? I hope students with experience can share it.

Answer 1

Wild pointer exception or access to a non-existent method without message forwarding

Bugly is just an auxiliary positioning tool. I am using Fabric for the same kind of problem, but it cannot be relied upon. I add global breakpoints to find the approximate location of the error, and carefully analyze the life cycle memory management. Accumulation of experience can greatly reduce the occurrence of such problems.