Le 04/03/2014 17:57, Thiago Macieira a écrit :
> Em ter 04 mar 2014, às 15:04:13, Yves Bailly escreveu:
>> When trying GCC, either on Linux or using MinGW, it works fine.
>>
>> Any hint about what may happen? is it a compiler bug, or something else?
>> Any idea about a workaround?
>
> Please valgrind your code. A heisenbug like this is probably memory smashing
> or a dangling pointer dereferencing.
Obviously it's a memory problem :-) And alas, valgrind doesn't work on
Windows...
I'll try to get some Windows tool.
FYI, trying on Linux with valgrind, it doesn't complain at all.
What I'm trying to understand is *why* it occures *only* when using Visual 2013
and using a QString... if I replace all "QString" by "std::string", it works
just fine. It even works fine if I add a "char const*"-based constructor to my
"S" class, thus bypassing the implicit QString's conversion.
For what I can see, it seems there's some troubles between QString and Visual
2013
initializer-lists implementattion.
Keeping searching...
--
/- Yves Bailly - Software developer -\
\- Sescoi R&D - http://www.sescoi.fr -/
"The possible is done. The impossible is being done. For miracles,
thanks to allow a little delay."
_______________________________________________
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest
