Re: Help DTrace gurus: suggestions for capturing a mis-allocated NSData object on a customer's system
Re: Help DTrace gurus: suggestions for capturing a mis-allocated NSData object on a customer's system
- Subject: Re: Help DTrace gurus: suggestions for capturing a mis-allocated NSData object on a customer's system
- From: Greg Guerin <email@hidden>
- Date: Mon, 22 Nov 2010 10:23:13 -0700
On Nov 21, 2010, at 9:28 PM, James Bucanek wrote:
Yes, that's true. But in this case, there's no reason to pre-fill
the structure. All of the elements that are going to be used are
filled in the read loop, so pre-initializing it to zeros is just
extra cycles.
Understood. I was just wondering if it might make a difference to
the "uninitialized variable" analysis if you initialized it
completely, rather than minimally. Technically, you're taking the
address of the entire struct when you say &batch, even though it's
only been partially initialized.
If there really is a bug in dataWithBytes:length: where it's keeping
a pointer it shouldn't, then one would expect this bug to appear more
often and more widely. But I know of no reports of this happening.
It's the kind of thing that begs for a well-isolated compilable example.
-- GG
_______________________________________________
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