On 5 June 2017 at 20:40, Michael Meeks <michael.meeks@collabora.com> wrote:
Sooo ... I think your code is golden; but we're going to need to
fix
the package/ code to avoid the bug.
https://bugs.documentfoundation.org/show_bug.cgi?id=97597#c28
Suggests (input from Kohei appreciated) - that we may need to do a
new
'seek' each time we come to reading some bytes from the underlying
package/ stream - to ensure that no other thread is messing with our
underlying stream position while we are reading compressed data from it =)
Perhaps we need a new file abstraction which deliberately has no seek
position in it's API, forcing client code to always specify a position when
doing read()/write()?
Then when we pass such a handle/object between threads, its use will be
correct by construction.
Context
Privacy Policy |
Impressum (Legal Info) |
Copyright information: Unless otherwise specified, all text and images
on this website are licensed under the
Creative Commons Attribution-Share Alike 3.0 License.
This does not include the source code of LibreOffice, which is
licensed under the Mozilla Public License (
MPLv2).
"LibreOffice" and "The Document Foundation" are
registered trademarks of their corresponding registered owners or are
in actual use as trademarks in one or more countries. Their respective
logos and icons are also subject to international copyright laws. Use
thereof is explained in our
trademark policy.