• 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 testing - printf and gdb
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Unit testing - printf and gdb


  • Subject: Re: Unit testing - printf and gdb
  • From: Chris Espinosa <email@hidden>
  • Date: Tue, 10 Jun 2008 07:57:47 -0700


On Jun 10, 2008, at 7:45 AM, Alan Shouls wrote:
Hi Aaron,

I think calls to cout from the unit tests place the messages in the build transcript. Have you looked there?

Thanks for this. Both stdout and stderr appear in the build transcript. This is enough to do some debugging.

Do you know it possible to get the debugger working while running tests?

Chris Hanson - Xcode: Debugging Cocoa framework unit tests

The process for C/C++ is generally the same.

Chris
 _______________________________________________
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

  • Follow-Ups:
    • Re: Unit testing - printf and gdb
      • From: Alan Shouls <email@hidden>
References: 
 >Unit testing - printf and gdb (From: Alan Shouls <email@hidden>)
 >Re: Unit testing - printf and gdb (From: Aaron Montgomery <email@hidden>)
 >Re: Unit testing - printf and gdb (From: Alan Shouls <email@hidden>)

  • Prev by Date: Re: Unit testing - printf and gdb
  • Next by Date: Re: Unit testing - printf and gdb
  • Previous by thread: Re: Unit testing - printf and gdb
  • Next by thread: Re: Unit testing - printf and gdb
  • Index(es):
    • Date
    • Thread