Ah, got it. Thanks!
Unfortunately, Guard Malloc doesn't appear to reveal anything special.
Here's the top several lines of my log:
GuardMalloc: Allocations will be placed on 16 byte boundaries.
GuardMalloc: - Some buffer overruns may not be noticed.
GuardMalloc: - Applications using vector inst
On Mar 16, 2011, at 10:31 AM, James Maxwell wrote:
> I wasn't sure how to enable Guard Malloc in Xcode 4, so I just ran it with
> the Allocations Instrument. Lo and behold, it doesn't crash. This didn't make
> much sense to me, so I tried running the release build, rather than the debug
> build.
Edit your Scheme and go to the "Run" section. Then go to the Diagnostics tab.
On Mar 16, 2011, at 12:35 PM, Sean McBride wrote:
> On Wed, 16 Mar 2011 10:31:26 -0700, James Maxwell said:
>
>> Okay, strange discovery.
>>
>> I wasn't sure how to enable Guard Malloc in Xcode 4
>
> Someone on the X
On Wed, 16 Mar 2011 10:31:26 -0700, James Maxwell said:
>Okay, strange discovery.
>
>I wasn't sure how to enable Guard Malloc in Xcode 4
Someone on the Xcode list could probably help there...
>, so I just ran it
>with the Allocations Instrument. Lo and behold, it doesn't crash. This
>didn't make
Okay, strange discovery.
I wasn't sure how to enable Guard Malloc in Xcode 4, so I just ran it with the
Allocations Instrument. Lo and behold, it doesn't crash. This didn't make much
sense to me, so I tried running the release build, rather than the debug build.
No crash. Switch back to debug..
oops... How do I enable Guard Malloc in Xcode 4?
J.
On 2011-03-15, at 6:45 PM, Greg Parker wrote:
> On Mar 15, 2011, at 4:10 PM, James Maxwell wrote:
>> I'm getting a crash in initWithCoder, which seems related to decoding a
>> property called "value", which is of type id. Sometimes this objec
Thanks Greg. The initWithCoder is indeed at launch, so Guard Malloc shouldn't
be a huge problem. I'll give it a try.
cheers,
J.
On 2011-03-15, at 6:45 PM, Greg Parker wrote:
> On Mar 15, 2011, at 4:10 PM, James Maxwell wrote:
>> I'm getting a crash in initWithCoder, which seems related to deco
On Mar 15, 2011, at 4:10 PM, James Maxwell wrote:
> I'm getting a crash in initWithCoder, which seems related to decoding a
> property called "value", which is of type id. Sometimes this object is an
> NSString, sometimes it's an NSNumber, and sometimes it's an NSArray. The
> crash only occurs i
