Re: XCode 3 Debugger bug?

FROM : John Stiles
DATE : Thu Nov 22 02:14:11 2007

If you can repro this in a sample app, or can send your app to Apple 
as-is, definitely file a bug.

In my experience the debugger has lots and lots of little issues like 
this, but they never reproduce in a test app; they only start to 
occur when you have a real full-sized app. Our large apps have many, 
many debuggability issues like this screenshot—lots of [$VAR 
whatever] instead of real values, missing variables, <out of scope> 
or <value> where real values ought to be, etc. It's very frustrating 
but there's no way to file a real bug on it because tiny test apps 
never reproduce the bug, and our bugs always get closed with "cannot 
reproduce" when we file them.


On Nov 21, 2007, at 4:48 PM, malcom wrote:

> Hello list,
> I was debugging an app of mine while I've encounter this strange 
> thing (take
> a look at screenshot). This is not the first time.
>
> <http://img442.imageshack.us/img442/1134/picture2pp3.png>
>
> There is an NSMutableArray declared and called pdFormat.
> As you can see it was allocated and inited. However I can't see 
> into the
> debugger.
> Some other objects has a <value value instead the address memory.
> Is this a sort of bug of xcode 3 or a mistake of mine? Is there a
> workaround?
> Thanks a lot
> malcom
> _______________________________________________
>
> Cocoa-dev mailing list (<email_removed>)
>
> Please do not post admin requests or moderator comments to the list.
> Contact the moderators at cocoa-dev-admins(at)lists.apple.com
>
> Help/Unsubscribe/Update your Subscription:
> http://lists.apple.com/mailman/options/cocoa-dev/jstiles%
> 40blizzard.com
>
> This email sent to <email_removed>