Re: Xcode 4.6.2: Unrelated code clangs "potential leak" of contextInfo
Re: Xcode 4.6.2: Unrelated code clangs "potential leak" of contextInfo
- Subject: Re: Xcode 4.6.2: Unrelated code clangs "potential leak" of contextInfo
- From: Quincey Morris <email@hidden>
- Date: Mon, 22 Apr 2013 18:10:46 -0700
On Apr 22, 2013, at 17:15 , Jerry Krinock < email@hidden> wrote: But I wonder which behavior should I report as a bug? Should clang be reporting my old-fashioned over-retained contextInfos when compiling with ARC as "potential leaks"? Or not?
What does the analyzer graph look like? (The one you get if you expand the disclosure on the error message.)
My *guess* is that the 'for' loop adds just enough complexity to the flow control that the analyzer doesn't try to track the usage of the autoreleased variable all the way to the end of the scope, and so it loses the knowledge that it is properly released. After all, there's no *actual* leak in that code, is there?
How about reporting it simply as "inconsistent behavior" in the analyzer, and leave it to the clang people to decide which is the correct analysis?
|
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden