You can perform your own crash-logging with PLCrashReporter. Typically, you write the crash log to a file and then send it to a server the next time the app starts. In order to prevent an infinite crash-reporting loop (there was one in an early version), you want to do things in a specific order: Read … Read more
I have modified it slightly so that the loading view is shown after a tiny delay, and this works fine! So it appears to be something within the same event loop! – (void)viewDidAppear:(BOOL)animated { [super viewDidAppear:animated]; // Show load [self performSelector:@selector(doit) withObject:nil afterDelay:0.1]; } – (void)doit { [self presentModalViewController:loader animated:YES]; }
Crashing on iOS 11 inside of CFNetwork
It looks like the problem is that SDL2 isn’t properly signed. There’s a ticket to fix the issue at https://bugzilla.libsdl.org/show_bug.cgi?id=2058. When you spawn an application from Xcode 5 with lldb, Xcode loads a plugin that will inspect modules your application loads, presumably to give you insight into your program. Xcode is set up to crash … Read more
Try deleting your .user and .suo files – these are the user options files that VS creates. You get a .user file for each project and a .suo file for your solution. When they get corrupted, odd things happen. Deleting them will make you lose little things like which project is selected as the startup … Read more
The 64-bit time stamp is the time application’s primary thread was created in 100-nanosecond intervals since January 1, 1601 (UTC) (this is known as FILETIME). The 32-bit timestamp is indeed in time_t format (it tells the time the module was created and is stored in the module’s header). I’d say 0x0002d160 is an offset from … Read more