Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!uunet!mcsun!hp4nl!telmail!neabbs!dirr
From: dirr@neabbs.UUCP (DIRK REISIG)
Newsgroups: comp.sys.amiga
Subject: Re: TrackSalve bug
Message-ID: <318763@neabbs.UUCP>
Date: 2 Mar 90 02:50:44 GMT
Organization: NEABBS multi-line BBS +31-20-717666 (13x), Amsterdam, Holland
Lines: 13


In article <??>, ellson@stsusa.com (John Ellson) writes:
>In article <314754@neabbs.UUCP>, 61394@neabbs.UUCP (DIRK REISIG) writes:
>> #-- cut here --## There is a bug in TrackSalve 1.000.  But it can be
> Could you please describe the effects of this bug.  Does it do any
> damage to files?
 
 It is a small piece of code which was never debugged.  The bug exists of
a branch to the next address, Lattice ASM never warned me for.  It falls
to a long branch to an odd address causing guru #3.  It is unlikely to
happen because the code is very rarely executed.  The bug only existed
if the salve function was activated.
 No other files are affected than those expected to be at the moment of
the guru (open, unflushed).