> >0x4c00048f =    stcmi   4, cr0, [r0], #-572
> >
> >Co-processor 4 is not a standard co-processor, so my guess is you are 
> >trying to execute data -- ie your program jumped to never-never land.
> 
> Hmmm, I guess a better question would be, "Why do I get this irregularly
> from make and cc when doing a make build?"  Is this a possible indicator
> of bad memory, perhaps?
> 
> --Ken

Possible, or it could be an indication of a kernel problem (a race or 
something like that).  For the memory problem, there is probably a 
diagnostic routine in the firmware which you can use to do memory tests.  
I don't know what it would be called though.

Richard.