Dalvik error: incorrect opt magic number (0xff ff ff ff)

[Matt Reimer]

I'm trying to bring Android up a new hardware, but am hitting this problem:

D/AndroidRuntime( 44):
D/AndroidRuntime( 44): >>>>>>>>>>>>>> AndroidRuntime START <<<<<<<<<<<<<<
D/AndroidRuntime( 44): CheckJNI is ON
W/dalvikvm( 44): DexOpt: incorrect opt magic number (0xff ff ff ff)
D/dalvikvm( 44): Stale deps in cache file; removing and retrying
D/dalvikvm( 44): DexOpt: --- BEGIN 'core.jar' (bootstrap=1) ---

D/dalvikvm( 46): Ignoring duplicate verify attempt on Ljava/lang/Object;
D/dalvikvm( 46): Ignoring duplicate verify attempt on Ljava/lang/Class;
init: untracked pid 44 exited

Any ideas of what this means, and how to fix it?

Matt

[fadden]

The "incorrect opt magic number" just means that the file didn't get
fully created last time through. The magic number at the top of the
file is the last thing written. If something goes wrong, or the
"dexopt" process crashes, the file remains incomplete.

Normally pid 44 (the runtime) would report the status of pid 46
(dexopt) when it finished, but for some reason pid 44 is crashing.
The log should show a summary line from pid 46, so it looks like pid
46 may be crashing as well. You need to figure out why these
processes are suddenly bailing.