When I use LLDB on Xcode 4.6 to debug my program ,the app will be no responding and when I use GDB it is OK,
but In the new Xcode 5 there is only LLDB can be used
who can tell me how can I fix my LLDB or reinstall it?
thx
Please try this procedure
Remove old versions of Xcode
Upgrade to Xcode 5.0.1
NOTE: GDB is no longer supported. LLDB will be installed automatically.
Please use a compatible version of OSX (10.9, Mavericks).
If this answer helps please click the checkmark to accept the answer.
Related
I upgraded my OSX to macOS Big Sur version 11.1. Ever since I got this problem when trying to sign in in Xcode:
at the time I had an earlier version of xcode (12.2). I upgraded to Xcode 12.3 and the problem disappeared but then I came back up again. What can I do to fix this?
What I tried
rebooting in safe mode, didn't help
upgrading Xcode, solved the problem temporarily
tried to rebuild the dynamic link editor cache as suggested here but it was a dead end:
sudo update_dyld_shared_cache –force
This tool is deprecated.
I'm using Xcode 4.3.2 and it tried to install an update to the command line tools.
I clicked the update button and Xcode told me that [my apple id] does not have access to Command Line Tools. (Contact Apple Developer Support to resolve account access issues.)
The problem happened with 4.3.1 too, I just did the update to 4.3.2 because I thought that it will resolve the issue.
My account is a paid Mac + iOS Developer account. I am pretty sure I should have access to these tools. But Xcode tells me I don't.
I logged in to the developer portal and checked for new Terms of Service too. Everything looks alright.
How can I install the update? Does anybody have a solution for this?
Yes its all over the Twitter... Just go to Apple Downloads and manually install it. They are investigating the issue as far as I know
Dominik Porada details the solution at Xcode 4.5 and iOS 5.1 Simulator, ie. download the old XCode 4.4.1 from Apple and pull out the simulation. Personally, I just copied the simulator from one of my other Macs that I hadn't upgraded XCode on yet.
Not sure if it's still relevant but xcode-select --install might do it.
I had the same problem last night after the update to Mountain Lion and Xcode 4.4.
This morning I tried to build something in xcode and it told me that developer mode wasn't enabled on the mac. Once I enabled it, I tried to download the command tools again and that happened to work fine now.
I've read every other thread on this and have tried everything but the "Build and Archive" function is determined not to be clicked.
I am running OSX 10.6.7 and Xcode 3.2.4. I am developing a MAC application and am trying to submit it to the Mac App Store, but to do this i need to run the Build and Archive feature, and I simply cannot figure out how to get it to run. I have heard about these "developer tools 1.1" from some other thread but cannot find those either. If you are about to say that that will fix things, then please link me, otherwise, any suggestions are greatly appreciated.
P.S. Yes im in Release Mode
Another answer could be that your active SDK should be set to Device not to simulator. You can find this setting in Project > Set Active SDK > Device.
Happy Coding..!
Figured it out... In order to Build and Archive with a Mac App (as opposed to iOS) you need Xcode 3.2.5 (maybe even 3.2.6) or better. So to all those with the same problem, make sure you are running the lasest version before trying ot Build and Archive.
i have snow leopard 10.6.3 installed via iAtkos..everything runs good even XCode as well.I can successfully build iPhone apps run them on the simulator and the device but when i use the "build and archive" option( for adhoc distribution or itunes connect ) XCode simply crashes..does anybody have a solution for this?
thanks in advance
btw XCode version 3.2.3(tried 3.2.3 as well same result,also in safe mode)
Mac OS X version 10.6.3
I had the exact same problem, and it turned out it was caused by a variable of wrong type in info.plist. My short bundle version was created as int instead of string.
I was getting the warnings about it, but it didn't seem relevant since the crash happened only when archiving, and normal building worked fine, the app ran fine. I suggest you check your benign looking warnings, one of them could fix the issue.
You might try 3.2.4 (available now).
I'm trying to use direct commands to gdb through xcode's console window when the program is paused. But the (gdb) prompt just accepts the carriage returns, and does nothing. Has anyone encountered this? I'm on the latest version of Mac OS X (10.6.2) with the XCode 3.2 beta.
If using a beta best to contact the beta mailing lists as this is the sort of issue the developers want to know.
If using a beta the first thing I would check is does this work using the previous production version
Also note that you might be under a NDA and so can only discuss with the developers.
This is a bug in the software, or an incompatibility with some setting in my system. Formatting my laptop and reinstalling the software fixed the problem.