On Jul 20, 2009, at 11:18 PM, Alexander Spohr wrote:
Am 21.07.2009 um 00:38 schrieb Tim Schmidt:
Is there any way to work around this
Yes: find your memory bug.
EXC_BAD_ACCESS almost always is a memory bug in your code.
atze
Obviously CG's bitblock transfers access unallocated memory in this
case. If I accidently free said memory it completely eludes me where
this might happen (I am pretty confident I don't release any of my
model/controller objects unintentionally (I tried running with all the
usual mallocdebug options as well as NSZombies). Furthermore all NIBs
are managed by NSViewController subclasses. Can anybody point me to
some advanced guides on NSTableView (beyond the class reference and
tables guide).
_______________________________________________
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
