Mailing Lists: Apple Mailing Lists

Image of Mac OS face in stamp
 
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: XCode 3.0 debugger - almost non-functional



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.

No matter what I do every single breakpoint I set stays orange when my app starts under the debugger.  But if I pause the app then 'continue' the breakpoints become enabled.  Like you said... "almost useless"... :)

On 10/31/07, Doug Knowles <email@hidden> wrote:
Hi,

I'm trying to get an app under development working under Leopard, and the debugger is proving almost useless.  There's plenty of room to believe that I'm doing something wrong, so I'll post my observations and see what shakes out:

- Often, when the debugger stops at a breakpoint, the call stack is displayed, but the variable pane is blank.

- Often, single-stepping sends the app and the debugger into limbo; I never reach the next line, and about all I can do is terminate the app and start over.

- Almost always, threads other than the main thread can't be examined.  As soon as I switch to another thread, the debugger display stops updating, and even the console window is non-responsive.

Maybe these are all related, and/or there's some setup I'm missing.

Any advice welcome.

TIA,
Doug K;


 _______________________________________________
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

_______________________________________________
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

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>)



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.