[SOLVED] C++ variables don't show up when debugging in Qt 5.1.1
I configured Qt 5.1.1 with this configure line when I built it…
./configure -xplatform linux-TIarmv7-sgx-g++ -prefix /usr/local/qt5.1egl -opensource -confirm-license -no-cups -opengl es2 -no-pch –v
When I try to debug my Qt application I am not able to add or see local c++ variables of my application in the Locals and Expressions window of QtCreator 2.8.1. I can see Qml variables when I set a break point in a qml file but it won’t show me my c++ variables when I put a break point in my cpp files. Is there a flag I am missing or a build step somewhere along the way I forgot.
These warnings are in the Application Output window. I am running this on am335x TI demo board that has TI SDK 6.0 on it...
Skipping deprecated .gdb_index section in /root/DevApps/projects/ProjectBlue/ProjectBlue.
Do "set use-deprecated-index-sections on" before the file is read
to use the section anyway.Remote debugging from host 192.168.1.2
Unable to find dynamic linker breakpoint function.
GDB will be unable to debug shared library initializers
and track explicitly loaded dynamic code.Could not load shared library symbols for 17 libraries, e.g. /usr/lib/libts-1.0.so.0.
Use the "info sharedlibrary" command to see the complete listing.
Do you need "set solib-search-path" or "set sysroot"
I just installed QtCreator 2.6.2 and the c++ variables show up just fine. I am able to fully debug but the Design view is now broken because 2.6.2 does not support QtQuick 2.1. I also installed QtCreator 2.7.0 and that is where the ability to debug c++ variables stops. I am not sure what changed between QtCreator 2.6.2 and 2.7.0 but at least I can debug now. It's just a pain because I have to switch between 2.6.2 when I want to debug c++ code and 2.8.1 when I want to use the Design view. Any ideas on what I can do to get c++ variables in the Locals and Expressions window of QtCreator 2.8.1?
For the full solution see here: https://bugreports.qt-project.org/browse/QTCREATORBUG-10205
_hjk added a comment - 24/Sep/13 3:32 PM
You need a full build of creator from current 'master' branch to use this patch.
If you want a simple workaround for your installed version, just remove the 'import submodules' _
Removing import submodules from gbridge.py fixed my issue