Light-bulb.
First, Xcode's project-wide search is returning only one instance of "remove"
for a Textual-contain-search-term-case-insensitive search. Grep returns
hundreds.
Second, I just remembered some release-only code I wrote that does, in fact,
try to remove from an array, and I forgot to
On Jul 9, 2013, at 19:14 , Scott Ribe wrote:
> Sometimes when the displayed call stack seems to make no sense, it's because
> you corrupted the stack. Do you have any stack-allocated arrays?
I have a number of @[ ] constructs in my code…
--
Rick
__
On Jul 9, 2013, at 7:08 PM, Charles Srstka wrote:
> Have you tried putting a breakpoint on objc_exception_throw
+1. That’s vital in any project. In Xcode 4 you can easily do this by just
going into the breakpoints tab and pressing the little “+” button at the bottom.
> or -[NSObject doesNotR
On Jul 9, 2013, at 7:39 PM, Rick Mann wrote:
> It only happens in release builds, and the call stack shown in Xcode while
> debugging shows no source. I can't figure out where the call is:
Sometimes when the displayed call stack seems to make no sense, it's because
you corrupted the stack. Do y
On Jul 9, 2013, at 9:00 PM, Rick Mann wrote:
> Yes, I'm aware of this fact. The problem is, I can't tell where the call is
> happening.
>
> Sent from my iPhone
Have you tried putting a breakpoint on objc_exception_throw or -[NSObject
doesNotRecognizeSelector:] ?
Charles
___
Yes, I'm aware. That's everything Xcode shows; that's the full stack. I had
hoped breaking on that message would break at the point of the send, not at the
point of handling the unrecognized selector.
Sent from my iPhone
On Jul 9, 2013, at 18:46, Jens Alfke wrote:
>
> On Jul 9, 2013, at 6:3
Yes, I'm aware of this fact. The problem is, I can't tell where the call is
happening.
Sent from my iPhone
On Jul 9, 2013, at 18:44, Maxthon Chan wrote:
> NSArrayI is one of the private subclasses of NSArray (not NSMutableArray) so
> there is no - (void)removeObject method. Consider check if
On Jul 9, 2013, at 6:39 PM, Rick Mann wrote:
> It only happens in release builds, and the call stack shown in Xcode while
> debugging shows no source. I can't figure out where the call is:
>
> #00x39f9f960 in objc_exception_throw ()
> #10x320fee06 in -[NSObject(NSObject) doesNotRecogni
I'm having a hard time tracking this down:
Jul 9 18:33:10 iPad-4G-64GB MatterScan[189] : -[__NSArrayI
removeObject:]: unrecognized selector sent to instance 0x1f097040
It only happens in release builds, and the call stack shown in Xcode while
debugging shows no source. I can't figure out whe
On Jul 8, 2013, at 20:28, Andreas Mayer wrote:
> It seems like when I call -setNeedsDisplay:YES the system is spawning a timer
> to do something later on and when those calls come in too fast, that timer is
> leaked.
>
> Any idea what I could do about that?
> (I tried calling -setNeedsDisplay:Y
I'm not quite sure how to make my popover (iPad) grow vertically to the size of
the content of the first view controller (a UITableViewController inside a
UINavigationController). I don't think I want it to resize whenever the content
changes, it should just size to fit (up to some maximum) when
CocoaHeads Lake Forest will be meeting on the second Wednesday of the
month. We will be meeting at the Orange County Public Library (El Toro)
community room, 24672 Raymond Way, Lake Forest, CA 92630
We will be discussing Hidden Gems in Cocoa and Cocoa Touch, some from the
WWDC talk of the same na
On Jul 8, 2013, at 18:04 , Jens Alfke wrote:
>
> On Jul 7, 2013, at 1:37 PM, Frederick Bartram wrote:
>
>> Have you tried using NSData to store C-arrays?
>
> Or alternatively use NSPointerValue to wrap a pointer to a malloc’ed C array
> as an object.
It seems to me that an array of float
13 matches
Mail list logo
