File Corruption

[Howard Bornstein]

>Have you found a repeatable recipe for creating the crash?  Once you have
>that, we can examine the objects, systems, and sequence of steps to hone in
>on the source of the problem.
>
>Sometimes diagnostics take some work, but I've never encountered a bug yet
>that could not ultimately be diagnosed.

Sorry for mixing terms. Perhaps what I've described isn't really "file 
corruption". But I would say that the stack somehow got corrupted.

Yes, it was a repeatable crash. No I couldn't find any obvious cause for 
this. This is where I become concerned about the IDE itself. The code was 
fine (demonstrated by cloning the card and having it work ok).

If the problem is in the IDE, my diagnostic choices are limited because I 
don't have the time to go through all the IDE code to see where it might 
be crashing. We buy develoment tools we can rely on, not that we can 
debug. :-)

>What's on that card?

A better question for you is, if you explicted wanted to make Rev crash 
by going to a card, what could you do to it to cause this to happen? The 
answer, I believe, is "nothing". You shouldn't be able to do anything 
using the normal development tools that would cause Rev to crash. So why 
did a normally-working card suddenly start crashing?

I agree with you that eventually the cause could be found. However, I'm 
suggesting that the cause is likely to be something internal to Rev (and 
I'm assuming it's the IDE, not the engine), not programming error. I 
would label this type of occurrance "corruption."

Since I found a quick method around the crash I took it (I have products 
to ship, you know), but if you or the Rev team is interested in 
diagnosing the cause of this crash, I think I've got a copy of the bad 
version of the stack around.

Regards,

Howard Bornstein
____________________
D E S I G N  E Q
www.designeq.com