Re: Strange memory corruption when using vector (works with deque)

[Francisco Vila]

2009/11/21 Han-Wen Nienhuys <address@hidden>:
> On Fri, Nov 20, 2009 at 3:35 PM, Reinhold Kainhofer
> <address@hidden> wrote:
>> While fixing bug 676, I ran into a very strange memory corruption situation:
>> Like in the tie-engraver.cc, I used vectors in tie-performer.cc to store the
>> moment together with the Audio_element_info.
>>
>> Now, this always led to memory corruption as soon as I called push_back.
>> Before the push_back call, the size() of the vector was 0, after the
>> push_back, the size() would be reported as 3303820998 (instead of 1)?!?!?
>>
>> Using a deque instead of a vector works just fine.
>>
>> In particular, the commit 4ba35b32beca41dce222a95a5e0ed0c959e867dd using
>> vector will always crash with the following file:
>>
>
> Can you point me to an online version of the suspect commits?

Is this what you ask for?

http://git.savannah.gnu.org/gitweb/?p=lilypond.git;a=commit;h=4ba35b32beca41dce222a95a5e0ed0c959e867dd

>> On the other hand, changing vector to deque in commit
>> b238aa006f301fe8c194a1329af75f9db9b3024b will work just fine.

http://git.savannah.gnu.org/gitweb/?p=lilypond.git;a=commit;h=b238aa006f301fe8c194a1329af75f9db9b3024b

-- 
Francisco Vila. Badajoz (Spain)
www.paconet.org
www.csmbadajoz.com