Search Results

Search found 4 results on 1 pages for 'coverstory'.

Page 1/1 | 1 

• Undefined symbols when attempting to use CoverStory with iPhone app: _vproc_transaction_end

  - by dbarker

  After following these steps to set up an iphone project with CoverStory, my build fails with two linker errors. Undefined symbols: "_vproc_transaction_end", referenced from: _gcov_exit in libgcov.a(_gcov.o) _vproc_transaction_end$non_lazy_ptr in libgcov.a(_gcov.o) (maybe you meant: _vproc_transaction_end$non_lazy_ptr) "_vproc_transaction_begin", referenced from: ___gcov_init in libgcov.a(_gcov.o) _vproc_transaction_begin$non_lazy_ptr in libgcov.a(_gcov.o) (maybe you meant: _vproc_transaction_begin$non_lazy_ptr) ld: symbol(s) not found collect2: ld returned 1 exit status The second error is similar to above, except for _vproc_transaction_begin. I'm using Xcode 3.2, GCC 4.2 on Snow Leopard. Any ideas what I'm missing?

  Read the article

• Problem when running gcov on an iPhone Project: profiling:/Users:Cannot create directory

  - by Blaine

  I have overcome all problems with setting up gcov on my iPhone project but now I am getting the following: profiling:/Users:Cannot create directory Does anyone have any suggestions as to what I might be doing wrong? I originally setup gcov following Google's instructions: http://code.google.com/p/coverstory/wiki/UsingCoverstory

  Read the article

• Setting up gcov in Xcode 3.1

  - by Algorithmic

  I'm trying to setup my Xcode project to be instrumented with gcov so I can determine the code coverage of my unit tests. All of the documentation I find online talks about settings that I don't find in Xcode 3.1, though. An example: To work with Coverstory, first you need to set up your target to work with gcov. This requires turning on "Instrument Program Flow", "Generate Test Coverage Files" and linking with the gcov library. (Using Coverstory) The closest thing I can find to "Instrument Program Flow" and "Generate Test Coverage Files" in my build settings is "Generate Profiling Code", which doesn't appear to do what I want it to do. Am I looking in the wrong place for these settings or are all of the examples I'm finding online stale?

  Read the article

• No test coverage files generated for Unit Test bundle in Xcode

  - by John Gallagher

  The Problem I've got a Cocoa project on the desktop and I'm using Xcode 3.2.1 on Snow Leopard 10.6.2. I want to generate code coverage files for my Unit Test Target in Xcode. What I've Tried As articles like this one suggest, I've adjusted the build settings to: “Generate Test Coverage Files” checked “Instrument Program Flow” checked “-lgcov” added to “Other Linker Flags” I've also set the Run Script section of the test target to have the following: # Run the unit tests in this test bundle. "${SYSTEM_DEVELOPER_DIR}/Tools/RunUnitTests" # Run gcov on the framework getting tested if [ "${CONFIGURATION}" = 'Coverage' ]; then FRAMEWORK_NAME=LapsusInterpretationEngine FRAMEWORK_OBJ_DIR=${OBJROOT}/${FRAMEWORK_NAME}.build/${CONFIGURATION}/EngineTests.build/Objects-normal/${NATIVE_ARCH} mkdir -p coverage pushd coverage find ${OBJROOT} -name *.gcda -exec gcov -o ${FRAMEWORK_OBJ_DIR} {} \; popd fi Since my Framework name is LapsusInterpretationEngine but my target is named EngineTests, I put this directly into the FRAMEWORK_OBJ_DIR but this didn't seem to help. I've tried cleaning before building. I've made sure all the above build settings apply to both the Unit Test Target and the Application Target. What I Get No .gcda or .gcno files anywhere in the build directory I'm using. I point CoverStory to the Objects-normal directory in my builds folder and it complains that there's nothing there for it to read. I must be doing something really obvious wrong. Anyone any ideas? I have tried the "EngineTests.build" directory being ${FRAMEWORK_NAME} and this gives the same results.

  Read the article

1