Stephen Kelly bedf0367ac QVariant: Fix flags for type-erased associative iterator key ... The flags here are passed to a private QVariant constructor, and they really represent a boolean - IsPointer or not. Because the flag for the key_type was incorrectly populated with the flag for the value_type, memory would be corrupted when using a mapping type whose value_type is a pointer, but whose key type was not, such as QMap<QString, int*> This typo has been there since the concept was introduced in commit v5.2.0-alpha1~807 (Add container access functionality for associative containers in QVariant., 2013-04-05). Task-number: QTBUG-52246 Change-Id: I9ecb13c603015eed2dc2ca43947fa0ecd6be8b5a Reviewed-by: Olivier Goffart (Woboq GmbH) <ogoffart@woboq.com>		2016-04-03 10:58:12 +00:00
..
stream	Split the QGuiVariant test from the Core one.	2012-07-25 00:48:33 +02:00
.gitignore	Moving relevant tests to corelib/kernel	2011-09-01 12:42:14 +02:00
qvariant.pro	Add C++11 if available for QVariant autotest	2014-11-13 15:21:07 +01:00
qvariant.qrc	Cleanup mess in public type ids.	2012-01-25 21:08:08 +01:00
tst_qvariant.cpp	QVariant: Fix flags for type-erased associative iterator key	2016-04-03 10:58:12 +00:00