On Feb 22, 2013, at 11:08 AM, Ken Thomases wrote:
> Well, I'm sorry that you're frustrated but many aspects of development
> require the application of human intelligence and can't be automated. This
> is one of them. If you actually go through the exercise of reviewing an
> object's retain/
I am not taking any sides here, but rather just interested in the topic at hand
: Tracking object references.
I had met an issue once that I never solved, which did require me to track down
retain / release calls. What I did was to find in my code every explicit or
implicit (@property
On Feb 22, 2013, at 7:42 AM, Matt Neuburg wrote:
> Some specific object did send "retain". It is that specific object's
> responsibility eventually to send "release". That's how Cocoa memory
> management works. Instruments *can* know, and *should* tell me, what specific
> object that is. I woul
On Feb 22, 2013, at 9:42 AM, Matt Neuburg wrote:
> On Sun, 17 Feb 2013 12:16:47 -0600, Ken Thomases said:
>> On Feb 17, 2013, at 11:50 AM, Matt Neuburg wrote:
>>
>>> On Sat, 12 Jan 2013 11:13:13 +, Mike Abdullah
>>> said:
The allocations instrument can show you all presently all
On Sun, 17 Feb 2013 12:16:47 -0600, Ken Thomases said:
>On Feb 17, 2013, at 11:50 AM, Matt Neuburg wrote:
>
>> On Sat, 12 Jan 2013 11:13:13 +, Mike Abdullah
>> said:
>>>
>>> The allocations instrument can show you all presently allocated objects.
>>> Find the object(s) you're interested in
On Feb 17, 2013, at 11:50 AM, Matt Neuburg wrote:
> On Sat, 12 Jan 2013 11:13:13 +, Mike Abdullah
> said:
>>
>> The allocations instrument can show you all presently allocated objects.
>> Find the object(s) you're interested in from that list and you can view its
>> history of being retai
On Sat, 12 Jan 2013 11:13:13 +, Mike Abdullah
said:
>
>The allocations instrument can show you all presently allocated objects. Find
>the object(s) you're interested in from that list and you can view its history
>of being retained and (auto)released, to figure out what is still holding ont
On 12, Jan, 2013, at 10:49 PM, Ken Thomases wrote:
> On Jan 12, 2013, at 11:34 AM, Martin Hewitson wrote:
>
>> On 12, Jan, 2013, at 12:13 PM, Mike Abdullah
>> wrote:
>>
>>> On 12 Jan 2013, at 09:01, Martin Hewitson
>>> wrote:
>>>
Dear list,
I'm still struggling to find the
On Jan 12, 2013, at 11:34 AM, Martin Hewitson wrote:
> On 12, Jan, 2013, at 12:13 PM, Mike Abdullah
> wrote:
>
>> On 12 Jan 2013, at 09:01, Martin Hewitson wrote:
>>
>>> Dear list,
>>>
>>> I'm still struggling to find the cause of a "CoreData could not fulfil a
>>> fault" error on saving an
On 12, Jan, 2013, at 12:13 PM, Mike Abdullah wrote:
>
> On 12 Jan 2013, at 09:01, Martin Hewitson wrote:
>
>> Dear list,
>>
>> I'm still struggling to find the cause of a "CoreData could not fulfil a
>> fault" error on saving an NSPersistentDocument (see other mail thread
>> "coredata coun
On 12 Jan 2013, at 09:01, Martin Hewitson wrote:
> Dear list,
>
> I'm still struggling to find the cause of a "CoreData could not fulfil a
> fault" error on saving an NSPersistentDocument (see other mail thread
> "coredata count not fulfill fault after object delete").
>
> I'm wanting to che
Dear list,
I'm still struggling to find the cause of a "CoreData could not fulfil a fault"
error on saving an NSPersistentDocument (see other mail thread "coredata count
not fulfill fault after object delete").
I'm wanting to check if some other object has a strong reference to the deleted
obj
12 matches
Mail list logo
