On Feb 4, 2016, at 11:12 AM, Dave wrote:
> Jeez, really? I need a broken debugger like a hole in the dead at the moment.
> Any idea what causes it and how to get rid of it? Using “po” won’t help as
> it’s a custom object, I need to look at the properties. Any ideas how I can
> do this?
OK.
On Feb 4, 2016, at 9:59 AM, Dave wrote:
> XCode 7.2 (7C68).
> Mac OS X (not iOS).
>
> Hi,
>
> I sent the following message to the XCode List, but now I’m wondering if
> there is a bug in my code that is causing this weird behaviour? What could
> cause then Debugger to think that a regular ob
> On Feb 4, 2016, at 7:59 AM, Dave wrote:
> What could cause then Debugger to think that a regular object is an
> Array/Dictionary?
The debugger is not perfect. You may need to use logging.
> The object in question is subclass from a custom base class.
Have you properly designed your custom
There are 100’s/1000’s of nodes, would take forever, I’m writing a self-test
method now…..
Shame about the debugger in XCode, still at least we have lots of lovely
animations to make up for it, thanks Apple.
I’m wondering if the cause of my problems is to do with archiving/unarchiving
as I’ve
I have traversed object hierarchies in the debugger using predicates and KVC in
GDB described below. (Last tested in Xcode 4.6.3 compiler Apple LLVM 4.2)
For an array, something like... (typed in mail )
po (NSArray*)[arr filteredArrayUsingPredicate:(NSPredicate*)[NSPredicate
predicateWithFormat:
Writing your own description or debugDescription method is a great way to view
a large custom object, since you can format it the way you like. For an
example, check out Apple's tech note about debugging magic (both OS X and iOS
versions of it) and look at theirs for a view hierarchy description
Hi Again,
I’m trying to debug a network of interwoven objects. To do all that with “po”
will take at least 10 times longer.
The only other way I can think to fix it, it to write a method on the Custom
Object subclass that Logs the Properties. Doing it that would would probably
take 3 or 4 time
The command po is for objects and p is for intrinsics; just add a typedef on
those. If what you mean by properties are actually instance variables, use the
-> operator on the object.
po [anObject aPropertyThatIsAnObject]
p (BOOL )[anObject aBoolMethod]
p anObject->aBooliVar
Unless you've modifi
Jeez, really? I need a broken debugger like a hole in the dead at the moment.
Any idea what causes it and how to get rid of it? Using “po” won’t help as it’s
a custom object, I need to look at the properties. Any ideas how I can do this?
I was wondering if it could be caused by a bug in my code
You're not alone. I see this every so often and just make do with the console
view to see what I need (po is your friend). If you have more than one project
open, you might try closing those before restarting Xcode. Another flake that
Xcode has is putting the wrong project's source file in the D
XCode 7.2 (7C68).
Mac OS X (not iOS).
Hi,
I sent the following message to the XCode List, but now I’m wondering if there
is a bug in my code that is causing this weird behaviour? What could cause then
Debugger to think that a regular object is an Array/Dictionary?
The object in question is su
11 matches
Mail list logo
