• 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
(no subject)
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

(no subject)


  • Subject: (no subject)
  • From: Tim Gogolin <email@hidden>
  • Date: Wed, 19 Nov 2003 14:44:02 -0600

My situation:
I have an app (built in xcode) that can detect an internal error situation and post a modal dialog that helps me understand part of the problem. The dialog is posted via [myApp runModalForWindow: w], so the stack is still intact. If I switch to the terminal, run gdb, and "attach" to the process I can get a good back trace.


Presumably I could continue to debug from the command line (ouch, command line debugging). The project is open in xcode and I launched the app from xcode (but not by using the "debug" command). Is there any way to "change my mind" and get the debugging UI up and running, in the same way that command line gdb will allow one to start debugging after the app has already been running normally?

--
Tim Gogolin
_______________________________________________
xcode-users mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/xcode-users
Do not post admin requests to the list. They will be ignored.

  • Follow-Ups:
    • Re: (no subject)
      • From: Jim Ingham <email@hidden>
    • Re: gdb attach ex post facto (was: no subject)
      • From: Chris Espinosa <email@hidden>
  • Prev by Date: Re: Xcode cross-developing to 10.1 and NSProgressIndicator (Modified by Justin Lundy)
  • Next by Date: Re: gdb attach ex post facto (was: no subject)
  • Previous by thread: (no subject)
  • Next by thread: Re: gdb attach ex post facto (was: no subject)
  • Index(es):
    • Date
    • Thread