i'm developing iPhone apps. Yesterday i updated leopard to snow leopard. Alongside i made the jump from XCode 3.1.4 to 3.2.4
I was always quite happy with XCode - working most of the time under windows, I really appreciate how well the XCode toolchain works together.
however - i'm not happy with 3.2.4 at all. i experience a lot of flaws, mainly with debugging. When an error arises, the debugger often stops at another place than the actual error happened. Sometimes the debugger does not trap into breakpoints at all and i get after some time a Error from Debugger: mi_cmd_stack_list_frames: Not enough frames in stack - whatever that means. And also I get invisible breakpoints which i can't remove anymore.
Does anyone experience similar things with XCode 3.2.4? if so, which is the newest release that works well?
Thanks!
Usually the problem is to do with level of debug symbols or some compiler optimization (which shouldn't be applied in debug builds). Maybe the information here will help.
Also try a complete clean (delete the build folder, remove the app from the device/simulator) & rebuild. Ensure you're working with the Debug configuration.
Related
I have an extremely annoying problem!
Xcode 7 crashes almost on every breakpoint when it tries to symbolicate.
I have done several things including deleting Xcode and reinstalling it...
I also had the same issue on the previous Xcode 6.X
Any clue? I am wondering if I should reinstall mac OS from scratch...
I solved the issue by changing the optimization level in the build settings, make sure it is set to None for Debug configuration and make sure your RUN scheme uses Debug configuration.
I'm currently migrating an old OS X project from Xcode 3 GCC to Xcode 4 LLVM.
The migration has so far gone fine. I've updated the code from 10.4 to 10.6, with a lot of deprecated API, and it all compiles just fine.
But when I try do debug using LLDB, I get the following error:
error: failed to launch '/Users/trenskow/Library/Developer/Xcode/DerivedData/The_Famous_Web_Editor-ddfqhzdztzzgfrcxaaywyxgtahzx/Build/Products/Debug/The Famous Web Editor.app/Contents/MacOS/The Famous Web Editor'
The application runs fine on it's own (besides the runtime errors I am trying to debug).
When I switch back to LLVM GCC and GDB, it launches fine, but Xcode never stops at the breakpoints. The application stops, but I do not get any indication of a breakpoint is being hit by Xcode.
Long shot, but:
The Famous Web Editor
Xcode and the compiler can sometimes trip over spaces in the project/target name. This usually shows up in broken header or library search paths, so I'm not sure if it applies here. But it's certainly worth a try to rename the target so it contains no spaces.
First clear your DerivedData (/Library/Developer/Xcode/DerivedData/) delete every thing from there.
Now restart your XCode, Restart your device.
run Xcode
I have an iOS project that I've put in Dropbox to work with a few friends. The issue is that it seems to get "corrupted", so that after some time (after someone else has accessed the Xcode project file), when I try to go and open it again I get a Base SDK Missing error. In the Project Settings, I discover that I'm missing the valid ARM6/ARM7 architecture for iOS apps—I can only choose from 32-bit or 64-bit Intel. My only other options are i386, various forms of PPC, and x86_64. I simply can't build for iOS anymore.
No one else that I'm working with seems to have this problem. It exists in both Xcode 3 and 4, so it's not an Xcode 4 issue either.
Is anyone else having this problem? Is there a fix?
In these cases it's often a good idea to 'Clean All Targets'. I have found that particularly after upgrades to XCode where platforms or architectures have changed, that XCode can become confused about the state of previous builds. Cleaning, then re-specifying your desired targets/architectures/etc and then rebuilding will work well.
Also don't forget that if you hold Alt (or Option) down when you click on the Active build settings drop down will give you additional options.
Can you reinstall XCode? Also, it might be wiser to host the project under source control.
Hehe...turns out that the project had been used under the 4.2 SDK and at the time I only had 4.0, which explained the missing SDK part...Updated to 4.2 and it's all fixed now.
Source control would've been nice, but there aren't that many good ones that support the features we need (for free); if anyone's got a guide to installing Subversion on OS X and using it (without being too technical read Terminal), I'd appreciate that. Or how to set up Git with Xcode 4 (although I know that's under NDA, so that's probably not going to happen).
I've got 2 applications using Core Data with a sqlite persistent store. I've got a data loader routine that I run to populate the CoreData DB from csv files. During development, when my data changes I run the routine from the simulator to generate new databases and copy the new one into the project.
This has been working quite well for XCode 3.2.3 and iOS 4.0. It even works in the XCode 4 Preview 2 and 3. I just installed the final version of XCode 3.2.4 and iOS 4.1. Now my db loader fails. It gives me no message, no warning, no nothing. It just dumps out to the spring board and XCode gives me the "Debugging Terminated" message. It will fail at different times during the load so I'm pretty sure it's not a data issue. I'm not doing any threading. I assume the issue has to do with either Core Data or sqlite, since that's when the crash occurs, but with no info reported I can't tell for sure.
I uninstalled everything. Xcode 3.2.4, Xcode 4 preview (assuming it was an issue caused by XCode 4) and reinstalled XCode 3.2.3/iOS 4.0. Things returned to normal. After getting some work done I attempted to upgrade to 3.2.4/iOS 4.1 again. I uninstalled 3.2.3/iOS 4.0, rebooted. Installed 3.2.4/iOS 4.1, rebooted and tried again. No luck. Same hard crash. Same lack of messaging as to the cause.
I have determined that this only happens with the Simulator with XCode 3.2.4, the device is fine as is XCode 4 and 3.2.3. I've tried playing with the target OS selection (3.0,3.1,4.0,4.1). I've tired adjusting the Compiler from GCC 4.0, GCC 4.2,LLVM GCC 4.2, LLVM 1.5. I've tried setting the Base SDK to iOS Simulator 4.1. Interestingly enough it will work in the iPad simulator when using the 3.2 SDK. So I've at least go that as a work around.
I guess there is one of 3 issues:
An issue with my code that has been uncovered by 3.2.4.
Bug in 3.2.4.
A configuration issue that I've missed.
If anybody has any troubleshooting ideas or answers I'd love to hear them. I've been doing iOS full time since V 2.1 and I am seriously stumped.
Thanks in advance,
I figured out my issue. It looks like the CoreData/Sqlite connection was a total red herring. Following a tip I read on SO, I used OSX's Console application and got a critical message "Failed to launch in time" that was not being displayed in XCode's debugger console.
It looks like the process was being killed due to what is essentially a timeout error. The iPhone will kill an application that takes too long to complete "didFinishLaunching." That's where I was kicking the data load routine off from. The new version of XCode must have adjusted it's timeout values.
So my takeaway is give OSX's console a shot if XCode isn't telling you everything and watch out for those red herrings.
When I upgraded I ran into troubles in the simulator when saving the managedObjectContext. I finally deleted my sqlite CoreData store file and have not run into similar problems. Try deleting your data file (well save a copy of it before deleting to see what is different).
Ok, this seems like a dumb question because MonoDevelop is getting more mature, so I'm sure I'm just missing it, but I looked around and all the questions about this subject seem to be about remote debugging or debugging on a Mac.
I'm using Ubuntu 10.04 Lucid Lynx, and I just installed MonoDevelop 2.2.1 from the software center.
I created a GTk# 2.0 project, added some widgets and code and everything seems to run fine. Then I added a breakpoint, and it shows up in my breakpoints window, and it says it's active, but the breakpoint never actually hits(stops execution and pulls me into the debugger).
I'm in Debug x86 mode, so I can't figure out what's going on.
Anyone have this happening/know what to do about it?
I'm having the same problem (also on Ubuntu 10.04) and found kind of a hack that is working for me. Instead of setting a breakpoint in the IDE (by clicking on the side or hitting F9), make a call to the System.Diagnostics.Debugger.Break() method in your code where you want the execution to break. After doing that, I am able to step through the code, use the immediate window, etc. Obviously, it's not a very good solution, but at least it's something.
To check whether you have a debugger installed, simply check whether the "Run" menu contains a "Debug" command.
You should be aware that Ubuntu ships a rather old version of Mono (2.4) which has no built-in "sdb" debugger, and its version of MonoDevelop 2.2 is patched to remove the sdb interface. To get semi-functional debugging, install the old "mdb" debugger - the mono-debugger and monodevelop-debugger-mdb packages, IIRC.
To get the best debugging experience (sdb), you need Mono 2.6+ and an unmodified MonoDevelop 2.2+. If you decide to build Mono from source, please read this and this first. Alternatively, you could use openSUSE, which has up-to-date Mono and MonoDevelop packages available.
What versions of Mono runtime and debugger are installed? I tried it with monodevelop 2.2 + mono 2.6 + debugger 0.0.0 under Windows and it works just like expected. Here is a quotation from mono's website, which may be helpful:
Mono comes with two Mono-specific debuggers: a hard debugger and a soft debugger, additionally, you can use the Unix GDB debugger with Mono to debug low level problems
...
Soft Debugger:
...
Moonlight, ASP.NET, Gtk#, iPhone and remote debugging supported
Maybe the problem is in a code? What do you mean by:
... (stops execution and pulls me into the debugger).