Re: Methods with Variable Numbers of Arguments
Re: Methods with Variable Numbers of Arguments
- Subject: Re: Methods with Variable Numbers of Arguments
- From: Joe Osborn <email@hidden>
- Date: Tue, 17 Dec 2002 22:04:39 -0600
Ah! Cool. Well, not-cool, but at least it makes sense.
After a bunch of mucking about, the problem finally went away. I
modified my test case a lot, and it seems to work... thanks for your
help. I think the problem can be traced to the testing framework I'm
using(Sen:Te OCUnit), but I'm not certain. Now weird things with
NSStrings vanishing and EXC_BAD_ACCESSes only show up while debugging,
but when running normally it all seems to go alright. OCUnit seems to
really dislike GDB...
Thanks for your help, Dr. Neuburg. ^_^
--j.osborn
On Tuesday, Dec 17, 2002, at 16:02 US/Central, matt neuburg wrote:
On 12/17/02 at roughly 3:30 PM, thus spake Joe Osborn <email@hidden>:
I'm just not sure where it could happen... I'm invoking the method
like
this:
OSBlock * block = [OSBlock blockWithString:@"[self
workEffectively];
return [NSData class];" nouns:self, [NSData class]];
So I don't see how anything could happen to the string constant I
feed.
I didn't say it was *that* string. I said it was *a* string. When
there's a retain error and a string vanishes, string pointers can
shift down and start pointing at the wrong thing. Sometimes it's
another string. Sometimes it's garbage. m.
matt neuburg, phd = email@hidden, http://www.tidbits.com/matt
pantes anthropoi tou eidenai oregontai phusei
Subscribe to TidBITS! It's free and smart. http://www.tidbits.com/
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.