This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: slice valarrays with std::string -> segfault
- From: Paolo Carlini <pcarlini at suse dot de>
- To: Paolo Carlini <pcarlini at suse dot de>
- Cc: Jhair Tocancipa Triana <jhair_tocancipa at gmx dot net>, gcc at gcc dot gnu dot org, Gabriel Dos Reis <gdr at integrable-solutions dot net>
- Date: Sat, 10 Dec 2005 21:32:55 +0100
- Subject: Re: slice valarrays with std::string -> segfault
- References: <87irtx8bcr.fsf@mandala.my-fqdn.de> <439B34F2.4000808@suse.de>
Paolo Carlini wrote:
>I think something is going wrong with types characterized by
>""non-trivial"" constructors, e.g., doing memory allocation from the heap.
>
>Gaby can you look into this?
>
>
Gaby, I see __valarray_copy used (instead of __valarray_copy_construct)
by the conversion constructor from slice_array for any type T: i.e., no
placement new, that cannot possibly work a T such as 'struct element' in
the posted snippet. Indeed, lots and lots of errors from valgrind...
Maybe there is something I'm missing in the Specs of valarray for the
conversion constructors?
Paolo.