• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Unit Test code coverage with Xcode 5
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Unit Test code coverage with Xcode 5


  • Subject: Re: Unit Test code coverage with Xcode 5
  • From: Daniel Vollmer <email@hidden>
  • Date: Fri, 04 Oct 2013 10:43:54 +0200

Hi,

On 2 Oct 2013, at 00:01, Simon Robbie <email@hidden> wrote:

> Best workaround I can come up with is to add a call to gcov in my tearDown methods:
>
> extern void __gcov_flush(void);
>
> - (void) tearDown {
>     [super tearDown];
>     __gcov_flush();
> }

I have no insight into this at all, but since exit() isn't called, this could maybe be a bad interaction of gcov with Sudden Termination?
Call [[NSProcessInfo processInfo] disableSuddenTermination] on startup (or add the equivalent plist-key) and see whether this helps.

	Daniel.


 _______________________________________________
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


References: 
 >Unit Test code coverage with Xcode 5 (From: Simon Robbie <email@hidden>)
 >Re: Unit Test code coverage with Xcode 5 (From: Simon Robbie <email@hidden>)

  • Prev by Date: Re: Docs all say preliminary
  • Next by Date: Xcode 5 nearly unusable
  • Previous by thread: Re: Unit Test code coverage with Xcode 5
  • Next by thread: 10.8.5 + Xcode 5, and nibs/xibs containing QTMovieViews
  • Index(es):
    • Date
    • Thread