• 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
Re: Help me interpret this initWithBytes/memcpy crash log?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Help me interpret this initWithBytes/memcpy crash log?


  • Subject: Re: Help me interpret this initWithBytes/memcpy crash log?
  • From: Shawn Erickson <email@hidden>
  • Date: Thu, 5 Jan 2006 10:14:21 -0800

On 1/5/06, Jonathan del Strother <email@hidden> wrote:
> I've seen a couple of these crashes submitted from users, and I can't
> quite figure out what's going on.

Exception:  EXC_BAD_ACCESS (0x0001)
Codes:      KERN_PROTECTION_FAILURE (0x0002) at 0x00000000

...snip...

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)
4   CoverFlow				    0x00011d34 -[ArtworkNode loadTextureFromImage] +
40 (crt.c:355)
5   CoverFlow				    0x000126e0 -[ArtworkNode loadTexture] + 256 (crt.c:355)
6   CoverFlow				    0x0000dff4 -[TextureLoader
demandTexture:artwork:] + 84 (crt.c:355)
7   CoverFlow				    0x0000ae34 -[Cover initWithAlbum:preloadTexture:]
+ 312 (crt.c:355)
8   CoverFlow				    0x00014aec -[Preloader loadTextures] + 568 (crt.c:355)
9   com.apple.Foundation		    0x928de6d4 forkThreadForFunction + 108
10  libSystem.B.dylib			    0x9002b200 _pthread_body + 96

...snip...

Seeing that this is a EXC_BAD_ACCESS I would guess that you are either
reading out into unmapped memory or writing out into unallocated
memory. Likely your length calculation for image data is faulting or
not fully validating things.

memcpy (and friends) are provided by the core of the system and is
mapped via a code page (at a well known/defined offset) so that is why
it shows up a littler differently then the rest.
 _______________________________________________
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

References: 
 >Help me interpret this initWithBytes/memcpy crash log? (From: Jonathan del Strother <email@hidden>)

  • Prev by Date: Re: Help me interpret this initWithBytes/memcpy crash log?
  • Next by Date: Re: Globaly unique NSManagedObjectID
  • Previous by thread: Re: Help me interpret this initWithBytes/memcpy crash log?
  • Next by thread: Weird socket/stream behaviour
  • Index(es):
    • Date
    • Thread