>I looked at the OS sources, but couldn't find any logical
>reason why it happens.
Look in DataMgr.c. You'll see it called a lot there.
This is one of those cases where you really want to know the function name one
call up. It would be really cool if there was a app which developers could tell
users to run which would capture a stack crawl at a fatal alert. It wouldn't be
hard to do. Just patch the alert trap to crawl up the stack and dump the names
to a preallocated buffer. The app could also check for common problems like
writing past the end of the stack or writing to a5 when it's not valid.
Anyways, you might find it hard to track down all the cases. Perhaps gremlins
can find a failing case?
-Roger Flores
