Android debugger does not work
-
I lost several days to understand the problem that is simply the last SDK ( no NDK ) , try using an older SDK without update, a new Qt5.5.0 version and recompile your project.
-
I lost several days to understand the problem that is simply the last SDK ( no NDK ) , try using an older SDK without update, a new Qt5.5.0 version and recompile your project.
-
@GGenny What version of the SDK are you using? I did something similar and went back to build tools 23.0 (current is 24.0) and turned off updates. but I am still getting no love from the debugger.
-
@sharethl Did you have to go back to "Platform SDK Tools" rev 22.x.x or the "Andoird SDK Platform Tools" rev 22 in Android SDK Manager? I am currently trying rev 22.6.2 of the SDK (the name of the tar.gz file) . I'll let you all know it goes, but I would rather be using the newest version that work, as this version doesn't support lollipop levels of API, android 4.4.2 is the highest level. Screen Grab of android sdk manager
-
@sharethl Thanks for sharing. I will definitely lodge a bug against this over for the newest Qt Creator. I wonder if I just missed somewhere in the notes that it wouldn't work with anything newer than 22.6 build of the SDK. It will certainly build and run just fine, it just won't debug. Thanks for your help and that of @sharethl . Now I just have to figure out why I can step through the init code but as soon as I enter the window app the gdbserver shuts down because of illegal memory access. Maybe I have to build the Qt .so files from scratch with debug symbols. Not sure though.
-
@sharethl Thanks for sharing. I will definitely lodge a bug against this over for the newest Qt Creator. I wonder if I just missed somewhere in the notes that it wouldn't work with anything newer than 22.6 build of the SDK. It will certainly build and run just fine, it just won't debug. Thanks for your help and that of @sharethl . Now I just have to figure out why I can step through the init code but as soon as I enter the window app the gdbserver shuts down because of illegal memory access. Maybe I have to build the Qt .so files from scratch with debug symbols. Not sure though.
-
@sharethl Did you have to go back to "Platform SDK Tools" rev 22.x.x or the "Andoird SDK Platform Tools" rev 22 in Android SDK Manager? I am currently trying rev 22.6.2 of the SDK (the name of the tar.gz file) . I'll let you all know it goes, but I would rather be using the newest version that work, as this version doesn't support lollipop levels of API, android 4.4.2 is the highest level. Screen Grab of android sdk manager
@john3000 Here is the list I have. Hate cannot upload image on here.
- Android SDK Tool Rev24.3.3
- SDK Platform-tools Rev 22
- SDK Build-tools Rev 22.0.1
- SDK Build tools Rev 20
- Adnroid API 22 and 19, SDK Platform
- Extras: Android support library Rev 22.2.1
I have two ubuntu PCs, 2nd PC with SDK Platform tools 23 cannot debug, once I copied the SDK mentioned above to 2nd PC, debug working.
I have Linux-Mint , 64 bits, android-ndk-r10e. -
Hello,
after your downgrade did you have any problems with gdb?
Because if i try to step into, after a little time I receive the message:
"The gdb process has not responded to a command within 40 second(s).".
As it is really slow....Do you think that I have to downgrade/upgrade it?
I'm on Windows 10 (...tried on Ubuntu, it works perfectly)Thank you.
-
@john3000 Here is the list I have. Hate cannot upload image on here.
- Android SDK Tool Rev24.3.3
- SDK Platform-tools Rev 22
- SDK Build-tools Rev 22.0.1
- SDK Build tools Rev 20
- Adnroid API 22 and 19, SDK Platform
- Extras: Android support library Rev 22.2.1
I have two ubuntu PCs, 2nd PC with SDK Platform tools 23 cannot debug, once I copied the SDK mentioned above to 2nd PC, debug working.
I have Linux-Mint , 64 bits, android-ndk-r10e. -
Please watch for https://bugreports.qt.io/browse/QTCREATORBUG-15032 and related bugs..
-
Hello,
after your downgrade did you have any problems with gdb?
Because if i try to step into, after a little time I receive the message:
"The gdb process has not responded to a command within 40 second(s).".
As it is really slow....Do you think that I have to downgrade/upgrade it?
I'm on Windows 10 (...tried on Ubuntu, it works perfectly)Thank you.