VM Crash Dump overwrites file

Just noticed this in D5. Maybe it's always been this way? When the VM
generates a "Dolphin Crash Dump Report", it seems to overwrite the
<img-name>.errors file. Since there may often be walkbacks as a
precursor to a hard crash, it would be handy if the report could be
appended to the file rather than overwriting it, thereby preserving all
that history.

-------------------------------------------
Bill Dargel            [hidden email]
Shoshana Technologies
100 West Joy Road, Ann Arbor, MI 48105  USA

On Sun, 05 May 2002 15:38:41 -0400, Bill Dargel <[hidden email]> wrote:

>Bill Dargel            [hidden email]
>Shoshana Technologies
>100 West Joy Road, Ann Arbor, MI 48105  USA

Probably I knew you lived in Ann Arbor. But if I did I forgot. I wonder why we
don't have lunch once in a while ...

Ronald E Jeffries
http://www.XProgramming.com
http://www.objectmentor.com
I'm giving the best advice I have. You get to decide whether it's true for you.

"Bill Dargel" <[hidden email]> wrote in message
news:[hidden email]...
> Just noticed this in D5. Maybe it's always been this way? When the VM
> generates a "Dolphin Crash Dump Report", it seems to overwrite the
> <img-name>.errors file. Since there may often be walkbacks as a
> precursor to a hard crash, it would be handy if the report could be
> appended to the file rather than overwriting it, thereby preserving all
> that history.

Thanks Bill. The file open code is missing a flag. #925.

Regards

Blair