QMetaType::create: don't leak memory if copy can't be made
QMetaType::construct will return nullptr if a copy is requested but if there is no copy constructor. In that case, the memory allocated in QMetaType::create will be leaked. This case is covered in the unit tests in template<> void testCreateHelper<QMetaType::Void>() so we can't assert in construct that a copy constructor is present if a copy is requested. Fixes static analyzer warning 618b1e6877f737df57c39fd35ad91cd4. Change-Id: Ic439b36b1f120b9d0f888efaeab2801d8acc13de Reviewed-by: Fabian Kosmale <fabian.kosmale@qt.io> (cherry picked from commit 90b51219ddc75c4dd2d171f2dba644e67d1e4a62) Reviewed-by: Qt Cherry-pick Bot <cherrypick_bot@qt-project.org>
This commit is contained in:
parent
69951fec45
commit
ef34c99077
@ -571,7 +571,7 @@ int QMetaType::id() const
|
|||||||
*/
|
*/
|
||||||
void *QMetaType::create(const void *copy) const
|
void *QMetaType::create(const void *copy) const
|
||||||
{
|
{
|
||||||
if (d_ptr) {
|
if (d_ptr && (copy ? !!d_ptr->copyCtr : !!d_ptr->defaultCtr)) {
|
||||||
void *where =
|
void *where =
|
||||||
#ifdef __STDCPP_DEFAULT_NEW_ALIGNMENT__
|
#ifdef __STDCPP_DEFAULT_NEW_ALIGNMENT__
|
||||||
d_ptr->alignment > __STDCPP_DEFAULT_NEW_ALIGNMENT__ ?
|
d_ptr->alignment > __STDCPP_DEFAULT_NEW_ALIGNMENT__ ?
|
||||||
|
Loading…
x
Reference in New Issue
Block a user