Ah, that was it! Thanks! -Laurent. -- Laurent Daudelin AIM/iChat/Skype:LaurentDaudelin http://nemesys.dyndns.org Logiciels Nemesys Software laurent.daude...@gmail.com Photo Gallery Store: http://laurentdaudelin.shutterbugstorefront.com/g/galleries
On Mar 10, 2010, at 14:24, Thomas Clement wrote: > Do you call CFRelease() on the returned host object? > If not, you should. > > Regards, > Thomas > > On Mar 10, 2010, at 10:56 PM, Laurent Daudelin wrote: > >> I didn't redefine the macro but for support of older OS X versions, I'm >> currently using LLVM GCC 4.2. Maybe that's why? >> >> >> >> >> -Laurent. >> -- >> Laurent Daudelin >> AIM/iChat/Skype:LaurentDaudelin >> http://nemesys.dyndns.org >> Logiciels Nemesys Software >> laurent.daude...@gmail.com >> Photo Gallery Store: >> http://laurentdaudelin.shutterbugstorefront.com/g/galleries >> >> On Mar 10, 2010, at 13:17, Ken Ferry wrote: >> >>> File a bug with the static analyzer that it should not do this. :-) I'm >>> not sure what's wrong here, because clang already knows about assert, >>> unless you redefined the macro. >>> >>> See <http://clang-analyzer.llvm.org/annotations.html#custom_assertions>. >>> >>> -Ken >>> >>> On Wed, Mar 10, 2010 at 12:09 PM, Laurent Daudelin >>> <laurent.daude...@gmail.com> wrote: >>> Just ran the build analyzer on my code and the analyzer flagged this as a >>> possible leak: >>> >>> host = CFHostCreateWithName(kCFAllocatorDefault, (CFStringRef)hostName); >>> assert(host != NULL); >>> >>> saying that on the "assert(host != NULL)" line, there was a potential leak >>> of the object allocated just above. How would one deal with that? >>> >>> -Laurent. >>> -- >>> Laurent Daudelin >>> AIM/iChat/Skype:LaurentDaudelin >>> http://nemesys.dyndns.org >>> Logiciels Nemesys Software >>> laurent.daude...@gmail.com >>> Photo Gallery Store: >>> http://laurentdaudelin.shutterbugstorefront.com/g/galleries >>> >>> _______________________________________________ >>> >>> Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) >>> >>> Please do not post admin requests or moderator comments to the list. >>> Contact the moderators at cocoa-dev-admins(at)lists.apple.com >>> >>> Help/Unsubscribe/Update your Subscription: >>> http://lists.apple.com/mailman/options/cocoa-dev/kenferry%40gmail.com >>> >>> This email sent to kenfe...@gmail.com >>> >> >> _______________________________________________ >> >> Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) >> >> Please do not post admin requests or moderator comments to the list. >> Contact the moderators at cocoa-dev-admins(at)lists.apple.com >> >> Help/Unsubscribe/Update your Subscription: >> http://lists.apple.com/mailman/options/cocoa-dev/thomascl%40free.fr >> >> This email sent to thoma...@free.fr >> > _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
