[Interest] Qt Creator Samsung Android gdb can't connect

Mon Nov 26 17:20:21 CET 2018

The "run" work normally I could see the debug trace coming in too. It's really during the GDB server connection that it fail.

There is not much into the windows but here's the
Application Output:
D libXXX.so: (null):0 ((null)): QML Debugger: Waiting for connection on port 52726...

Nothing into the General Messages or Debugger Console (even into info level).

I will try the 4.8 RC as soon as I can.

From: Interest <interest-bounces at lists.qt-project.org> On Behalf Of Stanislas RENAN
Sent: November 24, 2018 3:18 AM
To: interest at lists.qt-project.org
Subject: Re: [Interest] Qt Creator Samsung Android gdb can't connect

Hi,

Does run-as work on your devices ?

Best regards,
Stanislas RENAN
Le 23/11/2018 à 20:33, Jérôme Godbout a écrit :
Someone told me Android 8.1 could fix the problem with Samsung Tab A, sadly I did update the tablet but it did not fix the problem. Is there a way to put Qt Creator into a verbose mode to know what he is looking for? Because the following error is not helping me figuring out what is wrong with the Samsung device:
[cid:image001.png at 01D48579.4BBC84D0]

The compile output:
14:20:17: The process "C:/QtNew/5.10.1/android_armv7/bin/androiddeployqt.exe" exited normally.
14:20:17: Pulling files necessary for debugging.
14:20:17: Package deploy: Running command "C:/AndroidSDK/platform-tools/adb.exe -s 7daa5efb61fecb72 pull /system/bin/app_process D:/Code/build/GGI-AIX2019-Android_for_armeabi_v7a_GCC_4_9_Qt_5_10_1_for_Android_armv7-Debug/app_process".
14:20:18: Package deploy: Running command "C:/AndroidSDK/platform-tools/adb.exe -s 7daa5efb61fecb72 pull /system/bin/app_process32 D:/Code/build/GGI-AIX2019-Android_for_armeabi_v7a_GCC_4_9_Qt_5_10_1_for_Android_armv7-Debug/app_process".
14:20:18: Package deploy: Running command "C:/AndroidSDK/platform-tools/adb.exe -s 7daa5efb61fecb72 pull /system/bin/linker D:/Code/build/GGI-AIX2019-Android_for_armeabi_v7a_GCC_4_9_Qt_5_10_1_for_Android_armv7-Debug/linker".
14:20:18: Package deploy: Running command "C:/AndroidSDK/platform-tools/adb.exe -s 7daa5efb61fecb72 pull /system/lib/libc.so D:/Code/build/GGI-AIX2019-Android_for_armeabi_v7a_GCC_4_9_Qt_5_10_1_for_Android_armv7-Debug/libc.so".
14:20:18: Elapsed time: 00:28.

From: Interest <interest-bounces at lists.qt-project.org><mailto:interest-bounces at lists.qt-project.org> On Behalf Of Jérôme Godbout
Sent: November 20, 2018 7:54 PM
To: interest at qt-project.org<mailto:interest at qt-project.org>
Subject: [Interest] Qt Creator Samsung Android gdb can't connect

Hi,
I have an issue when I try to debug under Samsung device (Tab A 2017, S4 or Tablet S7) they all cannot start into debugging, the application start then the gdbserver cannot be reach and Qt Creator think the application is not started (splash screen is visible and wait for gdb), even if the trace are flowing back from the device. All other devices I have (Hopeland, LG...) don't display this problem. Anybody have any success with running Qt Creator debugger with Samsung Android device?
Sadly I need to debug a Bluetooth bug that only occur with Samsung devices and I'm kind of despair without any debugger.

Qt Creator 4.7.2, Qt 5.10.1, Android SDK 27, Android NDK 17.2.49.

Any tips would be welcome.

[36E56279]
une compagnie  [cid:image003.jpg at 01D48579.4BBC84D0]
RAPPROCHEZ LA DISTANCE

Jérôme Godbout
Développeur Logiciel Sénior /
Senior Software Developer

p: +1 (418) 800-1073 ext.:109

amotus.ca<http://www.amotus-solutions.com/>
statum-iot.com<http://statum-iot.com/>
[cid:image004.png at 01D48579.4BBC84D0]<https://www.facebook.com/LesSolutionsAmotus/> [cid:image005.png at 01D48579.4BBC84D0] <https://www.linkedin.com/company/amotus-solutions/>  [cid:image006.png at 01D48579.4BBC84D0] <https://twitter.com/AmotusSolutions>  [cid:image007.jpg at 01D48579.4BBC84D0] <https://www.youtube.com/channel/UCoYpQgsmj1iJZyDjTQ3x8Ig>

_______________________________________________

Interest mailing list

Interest at lists.qt-project.org<mailto:Interest at lists.qt-project.org>

https://lists.qt-project.org/listinfo/interest
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/interest/attachments/20181126/0d106271/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 5391 bytes
Desc: image001.png
URL: <http://lists.qt-project.org/pipermail/interest/attachments/20181126/0d106271/attachment.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image002.jpg
Type: image/jpeg
Size: 6751 bytes
Desc: image002.jpg
URL: <http://lists.qt-project.org/pipermail/interest/attachments/20181126/0d106271/attachment.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image003.jpg
Type: image/jpeg
Size: 1016 bytes
Desc: image003.jpg
URL: <http://lists.qt-project.org/pipermail/interest/attachments/20181126/0d106271/attachment-0001.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image004.png
Type: image/png
Size: 483 bytes
Desc: image004.png
URL: <http://lists.qt-project.org/pipermail/interest/attachments/20181126/0d106271/attachment-0001.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image005.png
Type: image/png
Size: 506 bytes
Desc: image005.png
URL: <http://lists.qt-project.org/pipermail/interest/attachments/20181126/0d106271/attachment-0002.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image006.png
Type: image/png
Size: 500 bytes
Desc: image006.png
URL: <http://lists.qt-project.org/pipermail/interest/attachments/20181126/0d106271/attachment-0003.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image007.jpg
Type: image/jpeg
Size: 713 bytes
Desc: image007.jpg
URL: <http://lists.qt-project.org/pipermail/interest/attachments/20181126/0d106271/attachment-0002.jpg>