• 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: Debugger has become dysfunctional for my project.
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Debugger has become dysfunctional for my project.


  • Subject: Re: Debugger has become dysfunctional for my project.
  • From: Chris Espinosa <email@hidden>
  • Date: Sat, 23 Sep 2006 21:36:35 -0700

On Sep 23, 2006, at 6:22 PM, Jeff Birac wrote:

The Debugger refuses to debug my Carbon app.


Yesterday, the Debugger worked just fine with my Carbon app, but it has become dysfunctional today.


A Build and Debug brings up the Debugger window and quickly displays the alert "Carbon Debug exited with status (1).  The Debugger is still running.  Use 'Restart' to debug again"; however, the Restart button (and menu item) remains dim (not enabled), so a restart is not possible.


I can Run the executable just fine, but I cannot successfully Attach the Debugger to the running executable.  When I try to Attach to the running executable, the Debugger shows the alert "Carbon Debug exited with status (11).  The Debugger is still running.  Use 'Restart' to debug again", but the executable is actually still running.  Notice the exit status changed from 1 to 11.


It sounds like your app crashes when the debugger launches it or attaches to it.  This is unusual but not unheard of.  Check Console.app to see if there is any backtrace there to diagnose where and how the application is crashing.

CONTROL EXPERIMENT:  The Debugger works just fine with the fresh vanilla Carbon app from the Xcode project templates.


Did I inadvertently set something (e.g., a project setting) the wrong way?  I do not think so, because I can try to debug a backup (which was debuggable a few days ago ) and the Debugger still fails.  What would cause the Debugger to become so uncooperative with my project/executable?


It's hard to tell without some diagnostics of how your app is crashing when run under gdb.  

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

References: 
 >Debugger has become dysfunctional for my project. (From: Jeff Birac <email@hidden>)

  • Prev by Date: Debugger has become dysfunctional for my project.
  • Next by Date: Re: glitch upgrading from Xcode 2.0 to 2.4
  • Previous by thread: Debugger has become dysfunctional for my project.
  • Next by thread: Why does the following refuse to compile?
  • Index(es):
    • Date
    • Thread