Kind of a left field prob I think. Made some minor changes and made a build. Really nothing that would cause probs. Just some minor value changes and taking out a couple lines of deprecated stuff like orientation.
XCode started crashing after a minute or two while using the profiler. The project built and installed fine. Actually, it kept running fine after XCode crashed. Tried it a couple more times with and without the profiler and pretty much the same but with no consistency of when it would crash. Then it stopped crashing but would terminate incorrectly. After that Debugger was giving me different info each time.
One thing that seemed consistent was if I hit the Home button a few seconds after our main menu loads, Debugger gave me an error about not enough stack frames. If I let it run for a while then the errors were different each time with no mention of stack frames. I don’t know what that error means but I don’t see how it could be overflowing the stack if that’s what it’s suggests. There isn’t much going on in the menu scene.
I made a fresh build (from Unity) of the exact project and it hasn’t been doing it (yet). I can’t say it’s fixed though and I can’t give a better description of the errors now. Any ideas?
I’m guessing it’s not a bug and pretty sure the project is solid. Some file got corrupted on build or xcode botched some index file or something. Just throwing it out in case someone has seen it. If so, I’ll try to reproduce and file a bug.
had some behavior just now that leads me to think it might be audio related. gotta double check some stuff (tomorrow!) and will try to report back if i can confirm.
been on a wild goose chase! xcode crashing appears to be a 1.5 problem. rebuilt in 1.02 and no crashes. again the app runs fine on the device. it’s xcode that crashes when i build from 1.5.
does 1.5 require the 3.x sdk be installed? i’ve only got 2.2.1 right now. guess i’ll give that a whirl…
to clarify, building for 2.2.1 is not the issue and the app runs fine on a 2.2.1 device. i didn’t have the 3.0 sdk installed at all. installed it which also updated me to xcode 3.1.3. looked good for a while but just crashed again now. argh!
i did, however, manage to catch the stack error in profiler on hitting the home button. this is a different issue than xcode crashing. might be related but xcode doesn’t crash on hitting home. it crashes while the app is running.
-> applicationWillTerminate()
Unknown error occured in:
No method at 0x3496d8c4
mi_cmd_stack_list_frames: Not enough frames in stack.
mi_cmd_stack_list_frames: Not enough frames in stack.
(gdb)
the best i could find on google is that it’s gdb bug. any other ideas?
won’t quite call this solved yet but in case it can save someone else the headache…
i was able to find some stuff in the crash logs that led me to blowing out my xcode.plist. seems to have done the trick for the crashes.
i’m going to assume the stack frames logging is the gdb bug i found on google. got that again one time. other runs it wasn’t there. didn’t crash tho! knocks on wood!
I had this same error today. According to the console, it was because I was attempting to change the Unity logo while using Unity basic… even though all I was doing was attempting to use one of Unitys landscape logos.
Sorry for the slow reply. My issue is different and I haven’t been able to suss it yet. My app doesn’t crash. Xcode does. So unfortunately, I don’t have a fix for you. I wasn’t doing anything with the Unity logo like tonyd but maybe it’s worth a try if you are.
The only thing I’ve been able to find on the mi_cmd error is that it’s a gdb bug. I don’t think it would be the source of your app crashing. Could there be something in one of your scripts that’s been deprecated?
Pete
think the stack is fine tho…