I'm trying to debug a program that has to run as root. I found a SO answer that explains how to use remote debugging to do that. The instructions there and similar instructions out there don't seem to apply to XCode 4. It's possible that I'm just not familiar with the "Executables" item that is referenced. Is there a way to do this in XCode 4?
There's currently no way to do this in Xcode 4. I've filed bugs regarding that lack, and would encourage you to do the same.
Related
In one project I'm using I can't set breakpoints in Swift code, Xcode always crashes when reaching one of them, doesn't matter if it's a "manual" or an exception breakpoint.
In other projects everything works as expected, only for one project Xcode 6.4 (6E35b) always crashes.
I tried cleaning, deleting derived data, resetting simulator, restarting Xcode/Mac - nothing helped at all.
Anyone else experiencing this problem and hopefully knows what helps?
EDIT
Seems only to be the case on one machine (Xcode 6.4, 10.10.5), but not on the other (Xcode 6.4, El Capitan). But as I mentioned in the comments, reinstalling Xcode didn't help, are there some other preferences I could reset/delete?
EDIT2
Here's the Xcode crash log file:
https://dl.dropboxusercontent.com/u/119600/Xcode_2015-08-12-074655_Stefans-iMac.crash
I would try uninstalling and reinstalling Xcode to see if it helps... I've heard of successes with this technique for similar issues.
Just delete the entire Xcode.app from /Applications, and reinstall from the .dmg. If you're not certain of the binaries and have time / bandwidth, consider re-downloading the .dmg.
If that doesn't work, try the following source control tricks (substitute "your favorite revision control" for "git"):
Try purging all objects not in source code control
Another approach: Check out the app again into a fresh repository (this will get even the files that may have been committed but ignored later).
If not under source code control, grab a .gitignore from here and add it to git, then check out into another directory (this will leave everything but source, interface builder, project files and resources/assets behind).
I'd suggest moving the breakpoint code to another location (such as making a function call and breaking either before or inside the function). However, if all Swift code has this problem, that may not work.
Finally, after making an interim commit (to roll back to), try it in Xcode 7 beta. Bit of a hassle because you have to upgrade to Swift 2.0, but if you keep the deployment target the same no iOS target changes are needed.
If this really is a burden and/or it's a small project, you could try creating a new project and migrating the files and storyboard over, but likely this is too much effort.
Either way, since you note it's pretty much all breakpoints in Swift code, file a bug with Apple's bug reporter. They really need to hear about issues such as this, since you don't seem to be alone in having this issue.
EDIT: Where are others seeing this issue?
Maybe we can see commonality -- since this is only reported in Swift projects (so far). A colleague has seen this problem with breakpoints (as well as stepping through code) in Xcode 6.4 on 10.10.4. (I've seen Xcode 6.4 crashes in the past as well).
I see OS version 10.10.5 mentioned as a target where this happens (#swalkner); is this a beta? If OS 10.10.4/5 is the only place we see this, it might be significant. If it's a project/OS interaction, it might be tricky to reproduce / fix, but I'd encourage everyone to submit detailed bug reports to Apple (maybe even link this post).
Some points to note if you're seeing this:
Operating System Version
Hardware
Target: Simulator vs. Hardware; iOS vs WatchKit app.
Target SDK version(s)
Swift only? Or on an Objective-C only project? Mixed?
Only one project, or several?
It's a longshot, but let me know if it's working:
uncheck the "Always show Dissasembly" check
Debug > Debug Workflow > Always Show Disassembly
In older versions of Xcode (<6.1):
Product > Debug Workflow > Show Disassembly When Debugging
I've just spent the past few hours trying to solve exactly the same issue.
I thought at first, it had started due to installing Xcode 7 on the same machine as Xcode 6.4. The problem certainly coincided.
However, due to having version control, I could look and see what files had changed since opening the project with Xcode 7.
The images.xcassets file had changed. Reverting this file back has stopped Xcode from crashing each time it hit a breakpoint.
I'm not sure whether this helps at all, but definitely look at images.xcassets and if needs be, delete it, recreate it and ensure it's setup 100%. It certainly fixed my issue.
I'm currently using xCode 5.1 and Objective-C to learn how to make apps and I'm wondering what would happen to my projects if I update from 5.1 to 6. Will my projects still run or will I have to code everything in Swift?
Your projects should still run if they were running in previous versions. What will most likely happen is that you will be bombarded by warnings and alerts about deprecated code and syntax. You're going to get a lot of them with an upgrade that big.
For the most part, XCode should tell you exactly what needs to be upgraded. It shouldn't change any of your code. But it's always good practice to back up your project.
Good luck!
See also : https://stackoverflow.com/a/24005402/4329655
I'm discovering XCode and iOS development.
Delving into the iOS documentation, I've tried to download and run some of the programming examples.
As an example, I'll use AccelerometerGraph.
If I download the code and try to compile, i get an error message, and I realize that the Navigation panel tells me : Base SDK Missing.
After fiddling around (the existing answers on stackoverflow refer to the Xcode 3.2 answer, which doesn't work) I figured I should go to "Editor > Validate Settingsā¦" and accept the changes.
It "seems" to work, (as in the "Missing SDK" message disappears, and I can compile) but I'm wondering if i'm missing something more fundamental.
Also, I thought if there is such a fundamental change, it would be useful to have it up there in one of the questions.
Thx
P.
Go to the project settings and choose "Latest SDK" for the SDK option and that should fix your projects.
And if you want to be super helpful, file a bug with Apple (at http://bugreporter.apple.com) and tell them to update these outdated sample projects to use the latest SDK's if possible.
Not missing something more fundamental. Apple's sample projects have a variety of vintages. Mostly they compile and link under the current versions of Xcode and friends. Some need to be brought up to date. What you found was one that was originally set up for an obsolete version of the SDK and it compiles and links fine with one that was automagically found on your system when you updated it.
I wonder whether I should start development of a new iOS project in Xcode 4 or 3.2 - on one hand, I know 3.2 (a little), there is lots of info about it out there, and it's stable and proven. On the other hand, Xcode 4 brings some improvements as well. Are the newer previews of Xcode 4 ready for prime time, or are they still too buggy?
I'm especially interested in issues with (and recommendations of) externally hosted repositories, as I was not very happy with how Xcode 3.2 played with the Subversion repository in my last project.
Which one to choose, and which (preferably free and externally hosted) repository to match?
Today (3rd Feb 2011) Apple released the GM-Seed of xcode4. It's now ready for usage and you can compile your apps and release to the app-store. So if you are new with xcode, I would suggest using xcode4.
Why?
The new compiler has a lot of optimizations done. The compiler (as far as I can see the results) generates faster code. It's big fun!
The new Userinterface is more reliable. It makes your development a lot faster!
2a. Interface builder is now integrated. You can "drag and drop" your userinterface Item using the "ctrl"-key into your code and xcode creates the source for you! This accelerates creation of userinterfaces a lot!
git support has been added to sourcecontrol, which makes development in teams easier
The new LLVM compiler shows errors immediately while coding. And it displays errors, which xcode3 never mentioned
In xcode4 Apple changed a lot! So if you start with xcode3, you will have a new learning curve with xcode 4. For newbs I suggest: Download the xcode4 goldmaster and get startet with xcode4!
I second JackPearse's endorsement of Xcode 4, with one caveat. Been using Xcode 4 for a couple of days and am really starting to like it. Particularly like the way it shows the changes in each file as you commit. Unfortunately, when you delete a file, it forgets that it will need to be deleted in the repository as well. But the big BUT right now is that Xcode 4 will immediately crash the moment you try to do any Core Data modeling. See also XCode 4 Data Model Versioning bug? here on Stack Overflow. So, if you plan to use Core Data, you'll need to keep Xcode 3 around as well until they fix this.
I've been looking around the web for an hour and I'm just giving up to ask it here...
I've got to work under Ada. I managed to make gnat work as a command line to compile my files.
But I want to be able to have proper projects in Xcode. My problem is that I've found some templates on the to make ada default templates, I've copy pasted them a bit everywhere (/library/developer/ application support etc) but they never appear in the list when I want to create a project.
My other problem is that when I create an empty project and add a .adb file to it I can't compile at all... How do I specify that I should use gnat with it?
I'm sorry for all these questions if they are stupid but I can't find the answer...
Two alternatives that may be of interest: the Ada plugin modules for NetBeans and the Ada 05 Language Module for BBEdit 9.x and TextWrangler 2.x .
FWIW, templates live in /Developer/Library/Xcode in Xcode 3.1.4.
If you are using the XCode Ada Plugin from here, it looks like it was made to work with Xcode 3.0. You might try downgrading to that and see if you have any better luck.
Personally, my IDE of choice is Emacs, so I can't go into any real detail about XCode past that. I'd suggest talking to the MacAda mailing list if you don't get a good answer here.