[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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

From: Francisco Vila
Subject: Re: Strange memory corruption when using vector (works with deque)
Date: Sat, 21 Nov 2009 07:40:50 +0100

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, I used vectors in 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?;a=commit;h=4ba35b32beca41dce222a95a5e0ed0c959e867dd

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

Francisco Vila. Badajoz (Spain)

reply via email to

[Prev in Thread] Current Thread [Next in Thread]