Daniel Baumann wrote:
therefore, it looks to me like an issue involving specific hardware
features/combinations/configurations/$whatever of the sparc machines in
question, rather than a generic sparc failure, thus lowering severity to
important.

Antonio, do you have an idea about that?

No, but I see in the build log that an invalid pointer seems to be passed to LZ_compress_close, so I am checking the related code in lzlib and plzip.

If I can't find anything wrong in the code, I'll release a new stable version of lzlib soon (maybe tomorrow) to see if that helps. There have been a number of changes in lzlib since 1.0.


Best regards,
Antonio.




--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]

Reply via email to