Re: Help me interpret this initWithBytes/memcpy crash log?
Re: Help me interpret this initWithBytes/memcpy crash log?
- Subject: Re: Help me interpret this initWithBytes/memcpy crash log?
- From: John Stiles <email@hidden>
- Date: Thu, 5 Jan 2006 10:49:22 -0800
On Jan 5, 2006, at 10:11 AM, Jonathan del Strother wrote:
... since srr0==lr...
Sorry, that's clearly not right. I must've gone cross-eyed after
staring at code for too long. In which case, the problem is that
the "exception was caused by a memory access instruction".
Presumably that implies the length overruns the actual data that
I've passed to initWithBytes ?
Is there much I can do to prevent this, other than coming up with
my own id3 loading routines? I mean, I'm passed a pointer to a
chunk of memory that supposedly contains the image, and the image's
supposed length. Is there any way to check that that chunk of
memory really does have that length before I pass it to
initWithBytes ?
Jon
You could use a signal handler.
A better solution would be to debug the id3 library you've got. I'm
just grasping at straws, but I'd guess the MP3 file in question is
corrupt somehow and the image length you're being provided is too
large. The code probably needs some sanity-checking.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden