Hello Julien,<div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><div class="im"><br>
Error: File /home/maryline/compile-<u></u>libreoffice/libo/clone/ure/<u></u>sal/cpprt/operators_new_<u></u>delete.cxx, Line 96: operator delete mismatch<br></div>
/usr/include/c++/4.6/debug/<u></u>safe_iterator.h:193:error: attempt to<br>
dereference a past-the-end iterator.<br>
<br>
Objects involved in the operation:<br>
iterator "this" @ 0x0xbe966380 {<br>
type = N11__gnu_debug14_Safe_<u></u>iteratorIN9__gnu_cxx17__<u></u>normal_iteratorIPSsNSt9__<u></u>cxx19986vectorISsN3rtl9Allocat<u></u>orISsEEEEEENSt7__<u></u>debug6vectorISsS8_EEEE (mutable iterator);<br>
state = past-the-end;<br>
references sequence with type `NSt7__<u></u>debug6vectorISsN3rtl9Allocator<u></u>ISsEEEE' @ 0x0xbe966380<br>
}<br></blockquote></div> <br>this helps a lot. We had a similar situation some days ago. When built with debug symbols some additional checks are performed to ensure that iterators are not missused. So it would be a good step if you could debug the unit test and as soon as you get a SIG ABORT get a backtrace and post it here or fix the problem. I think that we derefence vector::end() or something like this.<br>
<br><a href="http://wiki.documentfoundation.org/Development/How_to_debug#Debugging_cppunit_tests">http://wiki.documentfoundation.org/Development/How_to_debug#Debugging_cppunit_tests</a><br><br>Regards, <br>Markus<br>