Il 23/08/2016 14:52, Stephan Bergmann ha scritto:
On 08/22/2016 10:04 PM, Riccardo Magliocchetti wrote:
So I've built latest master with GCC thread sanitizer. Running make
check there's quite a lot of warnings: some duplicated, some with holes
in the stackstrace. You can find two of them attached. Is there
something useful?
The "WARNING: ThreadSanitizer: lock-order-inversion (potential deadlock)" are
not interesting as long as your problem is not a deadlock. There's
unfortunately always been quite some of those across the LO code base (as are
also reported by Helgrind, for example), but they seem to rarely cause problems.
Sometimes it segfaults and the stack trace is very similar to the one of these
warnings, sometimes it hangs and i have to kill the python process manually. So
looks related to me but i'm biased of course :)
--
Riccardo Magliocchetti
@rmistaken
http://menodizero.it
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.