| |||
| |||
| [Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] |
| I've searched through the archives, finding one similar instance of my problem last year, however the solution proposed does nothing for the programmers experiencing it. Several breakpoints are set for various classes in a project with a number of C++ and Objective-C classes. When the execution of the application hits a break point, sometimes the debugger hangs eventually terminating the application it is working with, giving an "exit with status (11) notification. This always happens with certain classes, but not with others that also have break points set. The debugger is taking up 99% + of the CPUs activity, so it appears to be a performance issue in the debugger at which point it eventually times out. I've made sure that it isn't an excessive amount of globals being viewed in the debugger (as in none displayed and the "savedGlobals" key in the .pbxuser file of the project bundle cleared). Anyone else experience this? I will be filing this in radar soon. Thanks in advance for any time in thinking or helping with this issue, Kevin (KJ) Walker Senior Mac Developer SmartSound Software, Inc. |
_______________________________________________ Do not post admin requests to the list. They will be ignored. Xcode-users mailing list (email@hidden) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/xcode-users/email@hidden This email sent to email@hidden
| Home | Archives | FAQ | Terms/Conditions | Contact | RSS | Lists | About |
Visit the Apple Store online or at retail locations.
1-800-MY-APPLE
Contact Apple | Terms of Use | Privacy Policy
Copyright © 2007 Apple Inc. All rights reserved.
