Re: addTabViewItem exception was:(no subject)
Re: addTabViewItem exception was:(no subject)
- Subject: Re: addTabViewItem exception was:(no subject)
- From: Jens Bauer <email@hidden>
- Date: Thu, 5 Feb 2004 23:06:51 +0100
Hi,
On Thursday, Feb 5, 2004, at 22:22 Europe/Copenhagen, J Nozzi wrote:
Don't know why the colon didn't come through - it's fine in my code.
However, the problem is solved. But I have NO IDEA how this happened.
There is code that gets executed before this method is called (to
update the NSTabView with a user-customizable list of tabs) that has
NOTHING to do with either the user-customizable list of tabs OR the
NSTabView instance themselves.
Apparently, another object was failing silently (when it should've
raised an exception). When I commented out the code to update the
NSTabView, I got the exact same exception, but in an entirely
different method, even though I stepped through before and it flagged
the addTabViewItem call when it died ...
It's as if there was a problem with the debugger. It was most
certainly flagging an unrelated line of code, yet I can only conclude
(out of sheer ignorance, admittedly) that when the allocation and
initialization of a totally different object in a different, unrelated
method failed, another object down the line fell into the resulting
pothole in memory? This is SHEER ignorant speculation, mind you, but
it's the only possibility that pops into my mind besides (gasp) a bug
in XCode.
... which isn't altogether improbable. There are all kinds of odd
happenings (yes, I've filed reports). Some of those problems can be
cleared up by cleaning the target. Others require completely
restarting XCode and IB.
I was going to suggest that you clean the target.
Make it a habit, that always before you make a release-build, quit
Project Builder or XCode, and delete the "build" folder, then open the
project and build again. This would ensure that you don't have some old
goodies from your last build affecting the new build. =)
But more than likely, it was a memory issue. Can anybody elaborate /
educate me here?
Heh, the only advice I can give you is: Don't leak memory, keep a lot
of free space on your harddisk, or even better: create a swap-partition.
It can be difficult to tell what happened, when it only happened once...
Love,
Jens
_______________________________________________
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.