Re: XCode 5.0.2 crashes constantly
Re: XCode 5.0.2 crashes constantly
- Subject: Re: XCode 5.0.2 crashes constantly
- From: Alex Hall <email@hidden>
- Date: Mon, 16 Dec 2013 08:22:41 -0500
On Dec 3, 2013, at 3:44 PM, Fritz Anderson <email@hidden> wrote:
> 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.
The vast majority are this:
-[DVTTextAnnotationAccessibilityProxyItem accessibilityActionNames]: unrecognized selector sent to instance 0x7fefbf248730
The instance is different for each, but most of the errors I see are that. There are a bunch of warnings:
DVTAssertions: Warning in /SourceCache/IDEFoundation/IDEFoundation-3582/Framework/Classes/Diagnostic/IDEClangDiagnosticActivityLogMessage.m:184
Details: Unable to create location for diagnostic.
mainFile: /Users/mehgcap/prog/xcode projects/audio game tests/OpenAL Tests/AITGameController.m
startLine: 4294967295, endLine: 4294967295, startColumn: 4294967295, endColumn: 4294967295
startFile: <NULL>
endFile: <NULL>
Object: <IDEClangDiagnosticActivityLogMessage: 0x7fefbf58ec40>
Method: -initWithDiagnostic:timestamp:pathMap:workingDirectory:documentURL:
Thread: <NSThread: 0x7fefbfd6db90>{name = (null), num = 63}
Please file a bug at http://bugreport.apple.com with this warning message and any useful information you can provide.
>
> 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.
Oddly, I don't see a crashed thread. It seems to be a list of a great many frameworks, with a hex value (memory address?) for each.
>
> - 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?
An OpenAL project, so the template is a standard OS10 app targeted at 10.9. This usually happens right after I compile and am trying to get to an error, whether with cmd-apostrophe or the issues table.
>
> - What does that target link to (Build Phases, Link Binary With Libraries)? Are any of the library names red?
I'm actually not sure where you want me to look for this one. Is there any accessibility tag on "red" libraries for Voiceover to pick up?
>
> - 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.
AudioToolbox, CoreAudio, OpenAL (al.h and alc.h), foundation of course, and a couple of my own classes. It's not a very complex project.
>
> 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
>
Have a great day,
Alex (msg sent from Mac Mini)
email@hidden
_______________________________________________
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