Hello,
On Mon, 2011-02-14 at 11:05 +0000, Michael Meeks wrote:
For me, saxparser crashes... I am debugging that but not really getting much
I wonder if the stlport iterators were simply more robust against
changes in the underlying structures. Is this a list it is iterating or
a hash ? If the latter then changes in the 'hash' had undefined (but
non-crashy) behaviour with stlport.
If it is the same crash we saw during FOSDEM, it is due to the fact that
with the hash_* containers of stlport, erasing the element pointed to by
the one-beyond-the-end iterator was graciously handled, whereas the
boost::unordered ones are crashing with it. But the fix is just easy by
checking whether the corresponding find did not return this kind of
iterator and perform the erase only then.
Cheers
Fridrich
Context
- Re: [Libreoffice] Problems with windows build (continued)
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.