Debug Builds: EXC_BAD_ACCESS in AppCode Build but not in Xcode Build

Hi all,

I'm working on a fairly large project in C++ (with bits of Objective C in the wrapper code), using the JUCE library as the base framework. I came across an odd issue the other day & have yet to solve it.

The issue is an easily reproducible EXC_BAD_ACCESS, and occurs only in the debug build that AppCode produces. It does not occur in the debug build that Xcode produces. The release builds from both work fine.

One theory is that AppCode has some stricter diagnostic guards set in its debug configurations, & the AppCode debug build is catching a dangling pointer or memory leak or whatnot that the Xcode build isn’t.

Has anyone heard of something like this before? Is there a way to see the command lines that AppCode uses when compiling, so I may see exactly the compiler settings used & check against Xcode?

Working on OSX 10.9.5, Xcode 6.1.1, AppCode 3.1

Many thanks!

Tad

1 comment
Comment actions Permalink

Hi Tad.

AppCode uses Xcode build system. It means that AppCode doesn't add some additional steps for the build process.

Is there a way to see the command lines that AppCode uses when compiling, so I may see exactly the compiler settings used & check against Xcode?


You can find it in the first line of build log (Messages toolwindow - Show Build Log button).

0

Please sign in to leave a comment.