4708 warnings...

[Thiago Macieira]

Em Terça-feira 05 Maio 2009, às 18:38:01, Benjamin Meyer escreveu:
> In a similar vain to warnings is console debug.  A year or so ago I  
> was trying out a version of Amarok and when running it from the  
> command line it spit out so much to the console that it was just  
> embarrassing.  The worst part was that when going back over and  
> reviewing what it had outputed there were several QObject::connect()  
> statements about incorrect connects.  There was so much "debug" that  
> the real errors were getting lost!  It is really a shame that KDE apps  
> dump so very much pointless stuff to the console when in release  
> mode.  When an end user runs your app there should be no output to  
> stderr by default unless it is a specific message to the user or an  
> actual error.  Just like with warnings when you have thousands of them  
> you miss the real errors.

Like I've been saying for a while, always run your applications with 
QT_FATAL_WARNINGS=1 when debugging them. All warnings will cause a SIGABRT, 
which you can easily catch in the debugger and fix.

-- 
Thiago Macieira - thiago (AT) macieira.info - thiago (AT) kde.org
  Senior Product Manager - Nokia, Qt Software
      PGP/GPG: 0x6EF45358; fingerprint:
      E067 918B B660 DBD1 105C  966C 33F5 F005 6EF4 5358
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/kde-core-devel/attachments/20090505/b299e446/attachment.sig>