[Interest] Fatal Q_ASSERT in 5.12.0-beta4?

[Olivier B.]

It seems that in commit
https://github.com/qt/qtbase/commit/f4169a633b97b7b6e7365172cf3d38d2f16a8914#diff-0e5a174e7dafaad904b9cb7af5a4c89c
of September 19th, an optimisation disable in VS project generator was
reverted. It initially was put to avoid the assert i get in QString
copy constructor, due to a bug in MSVC2010. Could it be that the bug
is still there in VS2015? I only get the issue with "-tp vc", not when
generating nmake makefiles
Le lun. 12 nov. 2018 à 13:00, Kai Koehne <Kai.Koehne at qt.io> a écrit :
>
> > -----Original Message-----
> > From: Interest <interest-bounces+kai.koehne=qt.io at qt-project.org> On Behalf
> > Of Olivier B.
> > Sent: Monday, November 12, 2018 12:33 PM
> > To: interest at qt-project.org
> > Subject: [Interest] Fatal Q_ASSERT in 5.12.0-beta4?
> >
> > I built 5.12.0-beta4 to prepare for the LTS, but qmake on my project aborts at
> > the assert in QStirng constructor. Trying to remove code to localize the
> > problerm, i get another assert in qvector.
>
> Please try to create a minimal example for the assert, and post it to bugreports.qt.io. Please also include a stack trace.
>
> > I am running the release qmake, and i never saw them in previous
> > (stable) versions. Are asserts enabled for beta releases or something?
>
> I'm not aware of any extra configuration for beta's that we don't also use in the final versions.
>
> Kai