On jeudi 22 décembre 2016 06:46:44 CET David Chapman wrote:
> If this is new valgrind behavior, I wouldn't discount a bug in its code
It certainly looks like one :)
> but the developers (not me) would need to know what the QVBoxLayout
> constructor is doing. If it's inlined, the call stack might point
> fingers at the calling function rather than the true offender.
It is not inline, and my call stack is from a non-optimized debug build
anyway.
> Does the QVBoxLayout constructor allocate any memory inside?
Yes but not with new[].
QVBoxLayout::QVBoxLayout(QWidget *parent)
: QBoxLayout(TopToBottom, parent)
{
}
QBoxLayout::QBoxLayout(Direction dir, QWidget *parent)
: QLayout(*new QBoxLayoutPrivate, 0, parent)
{
d->dir = dir;
}
--
David Faure, fa...@kde.org, http://www.davidfaure.fr
Working on KDE Frameworks 5
------------------------------------------------------------------------------
Developer Access Program for Intel Xeon Phi Processors
Access to Intel Xeon Phi processor-based developer platforms.
With one year of Intel Parallel Studio XE.
Training and support from Colfax.
Order your platform today.http://sdm.link/intel
_______________________________________________
Valgrind-users mailing list
Valgrind-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/valgrind-users
