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

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


  • Subject: FAQ: How do you debug a C++ Standard Tool Application?
  • From: Chris Espinosa <email@hidden>
  • Date: Fri, 24 Sep 2004 12:00:22 -0700

On Sep 24, 2004, at 10:57 AM, Laurence Flath wrote:
There are some interesting options in Xcode 1.5 for alternate I/O pipes, but the documentation isn't very helpful (Xcode Help). System console would be great if Console.app allowed keyboard input. The pipe option might also be useful if I knew where to attach... (Anyone?)

There's always the option of running gdb remotely, but if we were comfortable with that, we wouldn't be in Xcode. (:

They still have a way to go to match Visual Studio's debugging in terms of automatic watches, speed, and general ease of use. Both Xcode and VS seem to love hiding important settings in obscure places. But Xc seems to be getting better, while VS is just getting more complicated.

Laurence

On Sep 24, 2004, at 12:16 AM, Markian Hlynka wrote:

On Sep 22, 2004, at 10:30, Laurence Flath wrote:

This topic has been covered before on other lists, but...

Unfortunately the Standard I/O window in Xcode is a 'pseudoterminal'. For instance, you cannot use ncurses-type operations and have it behave the same as from within an actual shell (if I'm wrong here, I'd love to hear it).

'fraid that's my limited experience too; just forget it with ncurses. I wonder if there's a way to attach xcode to a gdb process running in a _real terminal... What do you think?


Use the standard Xcode trick to swap out running executables from under the Xcode (1.5) debugger:

1) Build your tool in Xcode.
2) Find the Executable that your target is going to run, and do Command-I
3) Go to the Debugging tab in the Info panel, and uncheck "Start executable after starting debugger"
4) Debug
5) In Terminal, launch your executable
6) In a separate Terminal window, use ps -axwww to find the PID of the process
6) Back in Xcode's debugger's gdb console, type "attach <PID>"


You should now be debugging in Xcode the process running in the Terminal window.


_______________________________________________ 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: FAQ: How do you debug a C++ Standard Tool Application?
      • From: Eric Albert <email@hidden>
    • Re: FAQ: How do you debug a C++ Standard Tool Application?
      • From: Laurence Flath <email@hidden>
References: 
 >XCode 1.5: Can't debug after performing Deployment build (From: Robert Cerny <email@hidden>)
 >Re: XCode 1.5: Can't debug after performing Deployment build (From: Robert Cerny <email@hidden>)
 >How do you debug a C++ Standard Tool Application? (From: Richard Dunlap <email@hidden>)
 >Re: How do you debug a C++ Standard Tool Application? (From: Wade Tregaskis <email@hidden>)
 >Re: How do you debug a C++ Standard Tool Application? (From: Laurence Flath <email@hidden>)
 >Re: How do you debug a C++ Standard Tool Application? (From: Laurence Flath <email@hidden>)

  • Prev by Date: How 'reliable' is MallocCheckHeap et al ?
  • Next by Date: Re: FAQ: How do you debug a C++ Standard Tool Application?
  • Previous by thread: Re: How do you debug a C++ Standard Tool Application?
  • Next by thread: Re: FAQ: How do you debug a C++ Standard Tool Application?
  • Index(es):
    • Date
    • Thread