| |||
| [Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] |
| Try turning off "Load Symbols Lazily" in the Debugging Pref pane. With Lazy Symbol Loading on, Xcode needs to know which module each source file is built into. With most Projects Xcode gets this right, but in some cases (.a files fool it sometimes, projects that build the same file into multiple targets, and most commonly Makefile targets built using Xcode where we have no idea what builds into what) we don't get this right. So it takes some other event to get us to read in the symbols. For instance, when we get the backtrace on stopping, we read symbols for any library we find in the backtrace. That's probably why interrupting causes your breakpoints to take. But the Lazy Symbol Loading is just an optimization. Turning it off may make the debugger start up more slowly, but everything will work correctly. Jim On Oct 31, 2007, at 6:56 PM, Simon Raisin wrote: Hey Doug do breakpoints work for you? I wish they worked for me. Jim Ingham Apple Developer Tools |
_______________________________________________ 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
| References: | |
| >XCode 3.0 debugger - almost non-functional (From: "Doug Knowles" <email@hidden>) | |
| >Re: XCode 3.0 debugger - almost non-functional (From: "Simon Raisin" <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.