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

[Neil Puttock]

2009/11/20 Reinhold Kainhofer <address@hidden>:

> Using a deque instead of a vector works just fine.

This still fails for me with --disable-optimising:

Program received signal SIGSEGV, Segmentation fault.
0x00000000005dc58e in Prob::internal_get_property
(this=0x7fff00cf8b30, sym=0x7ffff435abe0) at prob.cc:152
152       SCM s = scm_sloppy_assq (sym, mutable_property_alist_);
(gdb) bt
#0  0x00000000005dc58e in Prob::internal_get_property
(this=0x7fff00cf8b30, sym=0x7ffff435abe0) at prob.cc:152
#1  0x000000000069cc55 in Tie_performer::acknowledge_audio_element
(this=0xcf7ba0, inf=...) at tie-performer.cc:96
#2  0x00000000005c818b in Performer_group::acknowledge_audio_elements
(this=0xcf78e0) at performer-group.cc:53
#3  0x00000000005c83e3 in Performer_group::do_announces
(this=0xcf78e0) at performer-group.cc:90
#4  0x00000000005c8334 in Performer_group::do_announces
(this=0xcf6880) at performer-group.cc:79

Cheers,
Neil