Important: Please read the Qt Code of Conduct - https://forum.qt.io/topic/113070/qt-code-of-conduct

QtCreator: Can't find C++ debugger



  • Hi,
    since a few days i can't debug an anroid app with QtCreator (Env: Win7/64, QtCretor 4.6.1, Qt5.10.1, NDK r16b, build SDK 27) . The GUI is written using QML and the bussiness logic is written in c++. The application output show only "Can't find C++ debugger." and the app die. The debugger setup seems to be ok. I can start debugging without C++ (only QML) debugger. I can still debug windows application.
    Whats going wrong?



  • Meanwhile i have found the problem. The QtCreator 4.6.1 does not work with android debugging (at least for me).
    The issue is the same on Linux. I have installed the QtCreator 4.6.0-rc1 and the android debugging is now possible again. I'm wondering that no one has this issue. The QtCreator 4.6.1 is already released for a few days.


  • Lifetime Qt Champion

    Hi,

    Based on your setup, the one thing I can see is that you are not using the recommended NDK which is r10e (see the Android Getting Started guide).



  • @SGaist Thank you for reply. Yes, you are right but this was not a problem. I'm using the NDK r16b since at least 4 or 6 weeks and the debugging has worked even with the r16b NDK.


  • Lifetime Qt Champion

    Then can you show the complete error ?



  • @SGaist The only information i get is "Can't find C++ dbugger." (see screenshot). There is no compile error or any other that i can tell you.
    (0_1525856276694_QtDebugErr1.JPG image url)



  • @ad1170 said in QtCreator: Can't find C++ debugger:

    Yes, you are right but this was not a problem. I'm using the NDK r16b since at least 4 or 6 weeks and the debugging has worked even with the r16b NDK.

    That doesn't prove anything. There may have been a configuration conflict that may have caused everything to work correctly... One part of software reliability is that systems do not produce problems at one point, even if there is no apparent change made by the use.



  • @mvuori Might by, but i have never used the NDK 10. I have started development with NDK 13 and i never seen this kind of issue. But i will try to debug with the outdated NDK.



  • @mvuori said in QtCreator: Can't find C++ debugger:

    @ad1170 said in QtCreator: Can't find C++ debugger:

    Yes, you are right but this was not a problem. I'm using the NDK r16b since at least 4 or 6 weeks and the debugging has worked even with the r16b NDK.

    That doesn't prove anything. There may have been a configuration conflict that may have caused everything to work correctly... One part of software reliability is that systems do not produce problems at one point, even if there is no apparent change made by the use.

    I have rebuild the app using NDK 10e and try to debug, but the result is the same.



  • Meanwhile i have found the problem. The QtCreator 4.6.1 does not work with android debugging (at least for me).
    The issue is the same on Linux. I have installed the QtCreator 4.6.0-rc1 and the android debugging is now possible again. I'm wondering that no one has this issue. The QtCreator 4.6.1 is already released for a few days.


  • Lifetime Qt Champion

    Glad you found a workaround and thanks for sharing !

    4.6.1 being pretty new, you might be the first to hit that. You should check the bug report system to see if there's something related.

    The release notes might give you some clue about what has changed.



  • @SGaist said in QtCreator: Can't find C++ debugger:

    Glad you found a workaround and thanks for sharing !

    4.6.1 being pretty new, you might be the first to hit that. You should check the bug report system to see if there's something related.

    The release notes might give you some clue about what has changed.

    Already done... (https://bugreports.qt.io/browse/QTCREATORBUG-20403)


  • Lifetime Qt Champion

    Thanks, you should also add the SDK/NDK version you have on your system and that you tested several of them.



  • @ad1170 Sadly, you're not the only one experiencing this problem… https://bugreports.qt.io/browse/QTCREATORBUG-20379
    Hum, actually it is not exactly the same problem, as the debugger starts in the bug I've linked. But I do have the "Can't find C++ debugger." problem.
    Well, should not take long before it is fixed, as Bogdan has promised it : https://www.kdab.com/perfect-debugging-experience-with-qtcreator-on-android/ ;-)



  • Sadly is right. I've got an app that's days away from release and I can't debug. I've been suffering with this problem for months and NOBODY can help. Qt's debugging mechanism is flakey at best and I've very sorry the uppers didn't listen to me and go with Xamarin. I know this isn't the best way to get people to try to help but this sucks. Really sucks. It's unacceptable and there seem to be no options.


  • Lifetime Qt Champion

    Did you test the latest versions of Qt Creator ?
    Did you update the bug report with new information if your situation is different ?



  • @SGaist I am on the latest (4.6.2). However my debugger problems have been persistent through upgrades. To be clear, when I started using Qt, my Nexus 6P worked and my Note 4 worked. Then something (not sure what because it's been months) happened and my Nexus 6P stopped working. I think it was an Android update. All of a sudden I started getting an very descriptive error (I'm being facetious here): Connecting to remote server failed:
    Remote communication error. Target disconnected.: No error.

    So I stuck to debugging on the Note 4. But that is problematic too because it takes between 15 -25 seconds to step over or into. Then I upgraded to 4.6.1 and all of a sudden I started getting the error listed above (Can't find C++ debugger). Well, the debugger is there. So, I uninstalled everything: NDK, SDK, Windows SDK, Qt Creator... (multiple times) and followed the Qt documentation, installing everything over, paying extra attention to recommended versions and such. Now I'm on 4.6.2 and 5.11. Still the same. It's very frustrating as you can tell by my post.


  • Lifetime Qt Champion

    I completely understand. From what you wrote, it seems that an update to Android started to break things.

    You may have an unusual setup or maybe a combo of hardware/software that hasn't been encountered before. Ranting here won't help as this forum is not monitored by Qt developers. You should rather add these informations to the related bug report(s). That would help get things fixed more quickly.


Log in to reply