[Development] Programs crashing left and right in the CI

2016-07-22 Thread Thiago Macieira
For the past month or so, I've noted an increase in the number of crashes in 
applications that shouldn't be otherwise crashing. I first saw it with moc 
(Segmentation fault) and I thought my change was at fault. But it's been 
happening with other changes, even before my changes went in.

Now I ran into a link.exe internal error:

LINK : fatal error LNK1000: Internal error during LIB::Search

  Version 14.00.23918.0

  ExceptionCode= C005
  ExceptionFlags   = 
  ExceptionAddress = 7FF64939415B (7FF64937) "C:\Program 
Files (x86)\Microsoft Visual Studio 14.0\VC\BIN\amd64\link.exe"
  NumberParameters = 0002
  ExceptionInformation[ 0] = 
  ExceptionInformation[ 1] = 00020226BDF8

Can someone check whether there are memory problems in some of the CI 
machines?
-- 
Thiago Macieira - thiago.macieira (AT) intel.com
  Software Architect - Intel Open Source Technology Center

___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development


Re: [Development] Remember to rebuild qmake in dev

2016-07-22 Thread Thiago Macieira
On sexta-feira, 22 de julho de 2016 09:25:11 PDT Oswald Buddenhagen wrote:
> > To redo the configuration, I have to use:
> > 
> > cmd \ /c $QTSRCDIR/configure -redo
> 
> not sure what the cmd stuff is supposed to be good for, but it's correct
> that you *always* need to run the configure from the source dir (i.e.,
> the .bat file if you're building from git).

sh.exe can't run .bat files. You need to ask cmd to do it for you.

-- 
Thiago Macieira - thiago.macieira (AT) intel.com
  Software Architect - Intel Open Source Technology Center

___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development


Re: [Development] Remember to rebuild qmake in dev

2016-07-22 Thread Oswald Buddenhagen
On Thu, Jul 21, 2016 at 02:54:17PM -0700, Thiago Macieira wrote:
> On quinta-feira, 21 de julho de 2016 20:23:19 PDT Oswald Buddenhagen wrote:
> > On Thu, Jul 21, 2016 at 09:27:58AM -0700, Thiago Macieira wrote:
> > > moc.prf with MSVC now depends on a side feature in qmake to help support
> > > generating the moc_predefs.h file. If you're using MSVC, please remember
> > > to
> > > recompile qmake soon.
> > 
> > a much better recommendation is "run config.status (or configure -redo
> > on windows) *every time* after pulling". this ensures that qmake is
> 
> configure -redo on Windows doesn't work at all on a shadow build:
> 
> On one run:
> Unable to detect the platform from environment. Use -platform command line
> argument or set the QMAKESPEC environment variable and run configure again.
> See the README file for a list of supported operating systems and compilers.
> 
> On another:
> Invalid option "win32-icc" for -platform.
> See the README file for a list of supported operating systems and compilers
> 
> To redo the configuration, I have to use:
> 
> cmd \ /c $QTSRCDIR/configure -redo
> 
not sure what the cmd stuff is supposed to be good for, but it's correct
that you *always* need to run the configure from the source dir (i.e.,
the .bat file if you're building from git).

(which is why i'm actually considering generating a config.status.bat
file on windows.)
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development


Re: [Development] Remember to rebuild qmake in dev

2016-07-22 Thread Kai Koehne


> -Original Message-
> From: Development [mailto:development-bounces+kai.koehne=qt.io@qt-
> project.org] On Behalf Of Thiago Macieira
> Sent: Thursday, July 21, 2016 10:51 PM
> To: development@qt-project.org
> Subject: Re: [Development] Remember to rebuild qmake in dev
> 
> On quinta-feira, 21 de julho de 2016 18:02:51 PDT Mitch Curtis wrote:
> > It's probably worth pointing out what kind of errors we can expect
> > should we forget (so that we can recognise the problem).
> 
> The moc_predefs.h file contains qmake's help output, as opposed to a valid C
> source file. Since that file is consumed by moc itself, you're going to get 
> moc
> parsing errors.

Actually the qmake call already returns with an error code, so what you see is 
just something like

jom: D:\dev\qt\dev\msvc-2015-32\qtbase\src\testlib\Makefile.Debug 
[.moc\debug\moc_predefs.h] Error 2

with no previous error message.

Been there, done that :)

Kai
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development