[Interest] Qt debugging techniques?

[Richard Moore]

Oh, and I forgot to say - run gammaray!
https://www.kdab.com/kdab-products/gammaray/

Cheers

Rich.


On 15 February 2014 15:42, Richard Moore <rich at kde.org> wrote:

> A few useful things:
>
> You can set the QT_FLUSH_PAINT environment variable to see which parts of
> your widgets are getting repainted.
>
> You can set the QT_DEBUG_PLUGINS environment variable to see what's
> happening when Qt loads plugins (E.g. image formats)
>
> You can view all the requests passing through QNetworkAccessManager as
> detailed here
> http://blogs.kde.org/2010/05/01/qnetworkaccessmanager-proxy-classes
>
> You can get the details of what Qt sees when connecting to an SSL server
> as detailed here
> http://blogs.kde.org/2011/01/09/getting-details-ssl-connection
>
> You can make your SSL traffic decryptable by wireshark as detailed here
> http://peter.hartmann.tk/blog/2013/04/decrypt-ssl-traffic-of-qt-programs-in-wireshark.html
>
> Also many of Qt's subsystems have defines that can be enabled at build
> time to dump information about what they're doing as debug messages.
>
> Cheers
>
> Rich.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/interest/attachments/20140215/5cdf7dbe/attachment.html>