Re: [StrongED] Testing StrongHelp 2.90b1 (Urgent)

[Fred Graute <fjgraute@xxxxxxxxx>]

In message <mpro.on4bwl004yfpf0vz7.pittdj@xxxxxxxxxxxx>
          David Pitt <pittdj@xxxxxxxxxxxx> wrote:

[snip]

> I have now seen the crash after looking at the NeXTBar 1.30 StrongHelp.
> 
> It is a bit weird, it does not immediately crash !StrongHelp, that happens
> later on some other entirely innocent file.
>
> Paint gives a "Bad MODE" error but !StrongHlp can render it as can !Draw. A
> "corrected" version of the file can be extracted from !Draw after which
> there are no more crashes (yet?).

The sprite itself is actually fine. It's the data in the squash file
that is corrupted, there's some spurious data at the end.

StrongHelp allocates space based on the original length that's given in
the squash header. Because of the extra data the allocated output buffer
is overrun. This corrupts the list of free blocks so next time SH needs
to allocate memory (eg when opening a manual) it may hit the damaged
part of this list and abort.

Extracting the sprite and re-squashing it gets rid of the spurious data.
This stops the corruption of the list of free blocks and therefore SH no
longer crashes on manuals opened after the NeXTBar manual.

Cheers,
Fred.

-- 
StrongED Developer
http://www.stronged.iconbar.com/

--=20
To unsubscribe send a mail to StrongED+unsubscribe@xxxxxxxxxxx
List archives at http://www.Torrens.org/RO/StrongED/index.html