[Interest] Debugging in Qt Creator and displaying Qt objects d_ptr members in watch window ?

Edward Sutton edward.sutton at subsite.com
Thu Sep 17 17:52:51 CEST 2015

Thanks Michael.  Thanks Daniel.

It sounds like Visual Studio is still the best development environment in 2015 and beyond.

I think I will get the VS 2013 Qt Plugin and start my Windows VM as my main development machine.  Qt Creator has been crashing unexpectedly lately anyway when I am editing source.


On Sep 17, 2015, at 10:02 AM, Michael Jackson <imikejackson at gmail.com<mailto:imikejackson at gmail.com>> wrote:

*External Message - use caution*

On Sep 17, 2015, at 9:45 AM, Edward Sutton <edward.sutton at subsite.com<mailto:edward.sutton at subsite.com>> wrote:

I spend too much time adding qDebug() statements because Qt objects d_ptr members are invisible to the debugger.

I use Qt 5.5 Enterprise pre-built to debug OS X, Android, iOS, and on Windows ( MSVC 2013 ).

Is the only solution to build Qt from source for all 4 platforms ?


Does building from source actually help? Our team has found the debugging situation on OS X basically hopeless. For general debugging we move to Xcode where the debugging in stable BUT you can not really inspect any Qt variables except for QString.

If we really need to debug Qt specific variables then we move the whole session to Windows and Visual Studio 2013 with the Qt plugin. The debugging experience there is the best all around that we have found.

We tried linux with LLDB but the root of the problem is the LLDB integration. It just does not work for what ever reason. Variables passed in by reference can not be inspected in the debugger. If you try to step "to fast" then LLDB or the LLDB Bridge code just hangs. If you "step" before the debugger has loaded the symbols then LLDB or the LLDB bridge hangs. If you step, but LLDB or the LLDB Bridge is still loading the variables view and you decide to step again, then everything hangs.

So basically if you want to really debug there are 2 solutions:
Windows with Visual Studio
Linux with GDB.

LLDB is just out. Xcode, Eclipse, CLion are NOT able to show Qt Variables in the debugger. All of the above are with nightly and release versions of QtCreator starting at 3.5.0 and newer.

Don't mean to be a complainer here, but just stating the situation as I have experienced it since last year. I wonder how much financial resources it would take to "purchase" the appropriate Digia engineer for a set amount of time to dedicate to fixing these issues?

Mike Jackson
Owner, BlueQuartz Software, LLC
Springboro OH USA.

This email and any files transmitted with it from The Charles Machine Works, Inc. are confidential and intended solely for the use of the individual or entity to which they are addressed. If you have received this email in error please notify the sender. Our company accepts no liability for the contents of this email, or for the consequences of any actions taken on the basis of the information provided, unless that information is subsequently confirmed in writing. Please note that any views or opinions presented in this email are solely those of the author and do not necessarily represent those of the company. Finally, the recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/interest/attachments/20150917/e24eef8b/attachment.html>

More information about the Interest mailing list