• 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: How do you debug a C++ Standard Tool Application?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: How do you debug a C++ Standard Tool Application?


  • Subject: Re: How do you debug a C++ Standard Tool Application?
  • From: Markian Hlynka <email@hidden>
  • Date: Mon, 27 Sep 2004 08:36:51 -0600


On Sep 27, 2004, at 0:46, Ken Turkowski wrote:


On Sep 22, 2004, at 11:15 AM, Richard Dunlap <email@hidden> wrote:

Debugging works fine, as long as you don't need stdin. Obviously,
program stdin conflicts with GDB's commands.

What am I missing? Does nobody debug applications the require stdin?

Use the oldest debugger: fprintf to print state information to a file, while you run the program normally from Terminal.



I think what he's missing is Debug->Run Log. Or possibly Std I/O log... I forget which. the console is for giving commands to gdb, the other to your application.



_______________________________________________ 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: 
 >Re: How do you debug a C++ Standard Tool Application? (From: Ken Turkowski <email@hidden>)

  • Prev by Date: AppleScript Build Phase and osacompile - problem with deployed scripts for users
  • Next by Date: NSString weirdness
  • Previous by thread: Re: How do you debug a C++ Standard Tool Application?
  • Next by thread: AppleScript Build Phase and osacompile - problem with deployed scripts for users
  • Index(es):
    • Date
    • Thread