...because the world doesn't have enough bloggers

Sunday, July 1. 2007

0x8badf00d

It appears that John Gruber has managed to crash his iPhone already. The crash log, captured on the way through his Mac to Apple, contains what looks to my eye as something a little ominous:
Exception Codes: 0x8badf00d

Now that is not the sort of thing to happen by chance. Furthermore the crash log doesn't seem to want to actually allocate blame for the crash to any particular thread or cause. Repeat after me: never buy the first iteration of an Apple product.

Lots of other interesting stuff in there too - binary images for an OpenGL-ES implementation, sqlite3 and frameworks called "CoreSurface" and "CoreTelephony". Hmmmmm.
Posted by David Preece at 12:17 | Comment (1) | Trackbacks (0)

Trackbacks
Trackback specific URI for this entry

No Trackbacks

Comments
Display comments as (Linear | Threaded)

There are quite a few places in Darwin/OSX that fill uninitialized memory with 0x8badf00d, in exactly the same way that AIX-influenced PowerPC CFM stuff filled memory with 0xdeadbeef.

They're memorable numbers that are unaligned and point to unmapped high memory, pretty much ensuring that you get an unhappy CPU if you use one as a pointer. Much better than 0.
#1 Bruce Hoult on 2007-07-29 18:27 (Reply)

Add Comment

BBCode format allowed
E-Mail addresses will not be displayed and will only be used for E-Mail notifications.

To prevent automated Bots from commentspamming, please enter the string you see in the image below in the appropriate input box. Your comment will only be submitted if the strings match. Please ensure that your browser supports and accepts cookies, or your comment cannot be verified correctly.
CAPTCHA