Debugger has become dysfunctional for my project.
Debugger has become dysfunctional for my project.
- Subject: Debugger has become dysfunctional for my project.
- From: Jeff Birac <email@hidden>
- Date: Sat, 23 Sep 2006 21:22:46 -0400
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.
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?
Thanks.
-- Jeff
_______________________________________________
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