Re: XCode 5.0.2 crashes constantly
Re: XCode 5.0.2 crashes constantly
- Subject: Re: XCode 5.0.2 crashes constantly
- From: Fritz Anderson <email@hidden>
- Date: Tue, 03 Dec 2013 14:44:14 -0600
On 3 Dec 2013, at 11:28 AM, Alex Hall <email@hidden> wrote:
> I am on Mavericks, with the latest Xcode (5.0.2). I am working to update a library someone gave me, which has tons of errors since it is older code intended for iOS that I want to use on the Mac. So, I fix some things, run, it fails, I fix, I run, and so on. Every two or three runs, though, Xcode crashes. Most people I found on Google who see Xcode 5.x crashes have them happen when adding files, or fixed the problem by updating (back with 5.0 or 5.0.1). I am already on the latest version, though, and my crashes are almost always right after I hit cmd-r and get the failure results. Is there anything I can try to get this fixed, or am I stuck? Thanks.
Not much to go on…
Open the /Applications/Utilities/Console app and see what you find in the All-Messages System log. Enter Xcode in the search field to filter everything else out. Look at the entries contemporaneous with the crash; if any of them have disclosure triangles next to them, click them.
Also, under Diagnostic and Usage Information > User Diagnostic Reports, examine the files with names beginning with "Xcode". You'll have a 40% chance of learning what the crash is related to, but it's better than a survey of every Xcode 5 crash ever discussed.
Post the following to the list; we may be able to add another 10% to the odds of seeing something useful:
- Look for the "crashed" thread in the crash reports. Post the stack trace for that thread.
- Discuss what your project/target is trying to produce. Apparently a library, ported from iOS to OS X, 10.9 SDK? What kind of library?
- What does that target link to (Build Phases, Link Binary With Libraries)? Are any of the library names red?
- Your crash seems to take place when you try to run an application that exercises the library. Same question about what libraries the app uses.
After all that, there might be a clue to what you might do for a workaround, but at least you'll know exactly what it is you can do nothing about.
Not to post to the list, because it's a firehose of information:
- Insert a Run Script phase at the beginning of both targets, shell:
/bin/sh
script:
echo 'Hello world'
and check "Show environment variables in build log". Run the problem build. Xcode may still crash, but probably not before putting that environment dump into the log (which I hope will survive). In the Log navigator, select that build, and the run-script phase, and Edit > Copy. Paste into a text editor. This will be too long to be useful on this list, but go through it and see if anything stands out, like residual references to iOS resources.
- Put those crash logs, the environment list, a .zip of your project, and a more precise description of your problem into a new report on bugreport.apple.com. It should let you in even if you have only an unpaid developer registration.
— F
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden