On Fri, 2011-01-14 at 21:41 +0000, Caolán McNamara wrote:
I ported over the disable-custom-memory allocator at runtime stuff to
the new allocator that LibreOffice is actually using. Hopefully that
doesn't break anything horribly on e.g. windows. That should make it
easier to valgrind LibreOffice "out-of-the-box".
Ah - this would be why I was thinking 3.3.0 was so valgrind clean
then ;-)
Thanks for doing that - badly needed ...
Hey ho,
Michael.
--
michael.meeks@novell.com <><, Pseudo Engineer, itinerant idiot
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.