• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Help me interpret this initWithBytes/memcpy crash log?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Help me interpret this initWithBytes/memcpy crash log?


  • Subject: Help me interpret this initWithBytes/memcpy crash log?
  • From: Jonathan del Strother <email@hidden>
  • Date: Thu, 5 Jan 2006 17:59:29 +0000

I've seen a couple of these crashes submitted from users, and I can't quite figure out what's going on. I'd greatly appreciate anyone's help in translating the crash log.
The entire log can be found here - http://www.steelskies.com/ initWithBytesCrash.txt



OK, the crash point is here:

Thread 1 Crashed:
0 <<00000000>> 0xffff8ad8 __memcpy + 824 (cpu_capabilities.h:189)
1 com.apple.Foundation 0x928c2fa8 -[NSConcreteData initWithBytes:length:copy:freeWhenDone:bytesAreVM:] + 404
2 com.apple.Foundation 0x928e93b0 +[NSData dataWithBytes:length:] + 64
3 CoverFlow 0x0002e12c -[ArtSource artwork] + 812 (crt.c:355)
(...)



Basically, I'm reading images from mp3's ID3 tags, and have just got a chunk of binary data from id3lib. I then create an NSData object from the binary data using NSData dataWithBytes:length.



The thread state is :

Thread 1 crashed with PPC Thread State 64:
srr0: 0x00000000ffff8ad8 srr1: 0x000000000200d030 vrsave: 0x00000000ff000000
cr: 0x24000445 xer: 0x0000000020000007 lr: 0x00000000928c2fa8 ctr: 0x0000000000001a90
(...)


Now, according to Apple's crash reporter tech note (http:// developer.apple.com/technotes/tn2004/tn2123.html), since srr0==lr, we've crashed while fetching instructions.
It's years since I've done much assembly, so I'm a little rusty and struggling to interpret this. Why should it fail fetching the instruction pointer for memcpy? And why is memcpy's library given as <<00000000>>? 0xffff8ad8 sounds like a magic number to me, but I can't find anything useful about it on Google.


Umm...I'm not sure where to go from here, so any pointers would be massively appreciated.

Thanks
Jon

Attachment: smime.p7s
Description: S/MIME cryptographic signature

 _______________________________________________
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

  • Follow-Ups:
    • Re: Help me interpret this initWithBytes/memcpy crash log?
      • From: Shawn Erickson <email@hidden>
    • Re: Help me interpret this initWithBytes/memcpy crash log?
      • From: Jonathan del Strother <email@hidden>
  • Prev by Date: Re: Switching NSDocument's undo manager
  • Next by Date: Re: Help me interpret this initWithBytes/memcpy crash log?
  • Previous by thread: Re: Switching NSDocument's undo manager
  • Next by thread: Re: Help me interpret this initWithBytes/memcpy crash log?
  • Index(es):
    • Date
    • Thread