> I don't think this problem is down to confusion over memory management
> necessarily.
Poor choice of words on my part...
--
Scott Ribe
scott_r...@killerbytes.com
http://www.killerbytes.com/
(303) 722-0567 voice
___
Cocoa-dev mailing list (Cocoa-de
On 1 Aug 2009, at 20:21, kvic...@pobox.com wrote:
At 12:09 PM -0600 8/1/09, Scott Ribe wrote:
Still though, Shawn's basic point is right: Ken is confused about
memory
management *somewhere* in his code.
well... i'm not sure i'd use the word confused, as i do understand
memory management
At 12:09 PM -0600 8/1/09, Scott Ribe wrote:
> i'm using pointer to pointer (sometimes called handles) because that
is what is required when using the usb aspects of the IOKit as
demonstated in apple's sample code.
FYI, Ken's right. The IOUSB stuff is odd-looking. You have instance vars of
t
> i'm using pointer to pointer (sometimes called handles) because that
> is what is required when using the usb aspects of the IOKit as
> demonstated in apple's sample code.
FYI, Ken's right. The IOUSB stuff is odd-looking. You have instance vars of
type IOxxx**, and then pass the addresses of tho
At 6:31 PM -0700 7/31/09, Shawn Erickson wrote:
On Fri, Jul 31, 2009 at 3:39 PM, kvic...@pobox.com wrote:
where interface and device are declared as follows:
@property ( assign, nonatomic) IOUSBDeviceInterface300** device;
@property ( assign, nonatomic) IOUSBInterfaceInterfac
On Fri, Jul 31, 2009 at 3:39 PM, kvic...@pobox.com wrote:
> where interface and device are declared as follows:
> �...@property ( assign, nonatomic) IOUSBDeviceInterface300** device;
> �...@property ( assign, nonatomic) IOUSBInterfaceInterface300**
> interface;
Why are you use a poi
At 5:01 PM -0600 7/31/09, Nick Zitzmann wrote:
On Jul 31, 2009, at 4:39 PM, kvic...@pobox.com wrote:
these errors don't happen every time and i've yet to be able to
determine a pattern that causes them. i realize that this is some
sort of memory corruption problem, but i'm at a loss as to how
On Jul 31, 2009, at 4:39 PM, kvic...@pobox.com wrote:
these errors don't happen every time and i've yet to be able to
determine a pattern that causes them. i realize that this is some
sort of memory corruption problem, but i'm at a loss as to how to
find it. i do have NSZombieEnabled set t
to a usb device. sometimes, but not always, i'm getting crashes
when i'm either releasing my IOUSBDeviceInterface300 or my
IOUSBInterfaceInterface300. the error i get on the console is:
malloc: *** error for object 0x102662970: incorrect checksum for
freed object - object was probably m
