--- Comment #5 from Nicolas Sicard <> 2011-01-31 22:50:35 PST ---
> Actually, I think I know what's happening (roughly speaking). This problem is
> caused by bug# 5058. 

I think you are right, these bugs look very similar.

It definitely is related to opAssign, since it never occurs when opAssign is
not redefined. This would also mean that the compiler-generated opAssign is
either not calling invariant() or calling it at the right time, after data is
properly initialized. But I don't know what happens behind the scene in this

Configure issuemail:
------- You are receiving this mail because: -------

Reply via email to