[cmake-developers] Storage reallocation inside std::vector causing memory problem when using variable_watch

[Yves Frederix]

Hi Brad,

> Thanks!  Please expand out the comment and commit message to avoid
> referencing the mailing list thread.  A reader should be able to
> understand the problem without following such links.

See attachment for an updated patch. Hope I didn't flesh it out too much ;)

>
>> Makes sense. I'm not sure, however, how to test if the compiler
>> supports move construction. A link on stackoverflow suggests to use
>> something like "201103L <= __cplusplus". Unfortunately this does not
>> work for, e.g., VS2012 as it still defines __cplusplus as 199711L.
>> What would be a good way of checking this?
>
> One could use a try_compile to check it.  See Source/Checks/*.cmake
> and their use in the top-level CMakeLists.txt file.  This may not
> be worth the time unless you're interested in it.

I don't have experience with try_compile, but I will probably give it
a try at some point. Thanks!

Yves
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0001-Relookup-the-variable-value-in-case-an-associated-Va.patch
Type: application/octet-stream
Size: 4373 bytes
Desc: not available
URL: <http://public.kitware.com/pipermail/cmake-developers/attachments/20160323/a52e310d/attachment.obj>