Geek asks and answers

Ad-hoc crash when testing with EXEC_BAD_ACCESS with llvm 2.0 compiler

I ported the current project from Xcode 3 to Xcode 4. The ad hoc compiler with the LLVM 2.0 compiler crashes on iPod Touch 2G (iOS 4.2.1), but it works well on the iPad (iOS 4.3). This never happened before upgrading to Xcode 4.

When I tested with debugging settings on the device, the crash did not occur. When I tested with a special configuration (duplicated from the version), it will crash. When I switch the compiler version in the ad-hoc configuration from "LLVM 2.0" to "LLVM GCC4.2" or "GCC 4.2", there are no crashes.

So I use "LLVM GCC 4.2" for ad-hoc and release the configuration as a workaround. But I want to know what are the possible causes of the accident.

I did not publish a crash report because it only talks about a failure in thread 0, the stack thread.

+3
source share
3 answers

Try Xcode 4.0.2, which contains a fix for LLVM Compiler 2.0 that fixes a problem with these symptoms.

Thank!

-Chris

+3
source

I think this is because the remote debugger could not connect to your application over the phone for any reason. Does your Xcode 3 project have Entitlements.plist with customization get-task-allow? Are you deleting debugging characters? Compiler Optimization? Look through the Organizer window in the console log for your device, and I'm sure you will see errors in com.apple.debugserverif you are sure that you have no other code problems.

, , , . "Release", Ad-Hoc, Xcode GDB , , , , . , , Xcode , .

, , , . , , .

+1

xCode 4.0.2, ! , : https://devforums.apple.com/thread/92279?start=50&tstart=0 ( Apple)

+1

More articles:


All Articles