Discussion:
Qt Creator Samsung Android gdb can't connect
(too old to reply)
Jérôme Godbout
2018-11-21 00:53:44 UTC
Permalink
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:***@01D4810A.BDE00BE0]
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:***@01D4810A.BDE00BE0]<https://www.facebook.com/LesSolutionsAmotus/> [cid:***@01D4810A.BDE00BE0] <https://www.linkedin.com/company/amotus-solutions/> [cid:***@01D4810A.BDE00BE0] <https://twitter.com/AmotusSolutions> [cid:***@01D4810A.BDE00BE0] <https://www.youtube.com/channel/UCoYpQgsmj1iJZyDjTQ3x8Ig>
Jérôme Godbout
2018-11-23 19:33:42 UTC
Permalink
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:***@01D48338.5B30A970]

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-***@lists.qt-project.org> On Behalf Of Jérôme Godbout
Sent: November 20, 2018 7:54 PM
To: ***@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:***@01D48338.5B30A970]
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:***@01D48338.5B30A970]<https://www.facebook.com/LesSolutionsAmotus/> [cid:***@01D48338.5B30A970] <https://www.linkedin.com/company/amotus-solutions/> [cid:***@01D48338.5B30A970] <https://twitter.com/AmotusSolutions> [cid:***@01D48338.5B30A970] <https://www.youtube.com/channel/UCoYpQgsmj1iJZyDjTQ3x8Ig>
André Pönitz
2018-11-24 03:27:09 UTC
Permalink
Post by Jérôme Godbout
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?
There's Windows->Views->Debugger Log containing the communication between Qt Creator
and the debugger, but I wouldn't bet there's something usable in there in this case.

Andre'
Stanislas RENAN
2018-11-24 08:17:50 UTC
Permalink
Hi,

Does run-as work on your devices ?

Best regards,
Stanislas RENAN
Post by Jérôme Godbout
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
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.
*Jérôme Godbout
*Sent:* November 20, 2018 7:54 PM
*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
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/>
<https://www.facebook.com/LesSolutionsAmotus/><https://www.linkedin.com/company/amotus-solutions/><https://twitter.com/AmotusSolutions><https://www.youtube.com/channel/UCoYpQgsmj1iJZyDjTQ3x8Ig>
_______________________________________________
Interest mailing list
https://lists.qt-project.org/listinfo/interest
Oliver Wolff
2018-11-26 07:32:16 UTC
Permalink
Hi,

Can you check, whether the error still happens in Qt Creator 4.8 RC1
(online installer in preview section or
http://download.qt.io/development_releases/qtcreator/4.8/4.8.0-rc1/)? We
fixed some errors on Android and the one you are having looks like
something we fixed.

Br,
Olli
Post by Stanislas RENAN
Hi,
Does run-as work on your devices ?
Best regards,
Stanislas RENAN
Post by Jérôme Godbout
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
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.
*Jérôme Godbout
*Sent:* November 20, 2018 7:54 PM
*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
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/>
<https://www.facebook.com/LesSolutionsAmotus/><https://www.linkedin.com/company/amotus-solutions/><https://twitter.com/AmotusSolutions><https://www.youtube.com/channel/UCoYpQgsmj1iJZyDjTQ3x8Ig>
_______________________________________________
Interest mailing list
https://lists.qt-project.org/listinfo/interest
_______________________________________________
Interest mailing list
https://lists.qt-project.org/listinfo/interest
Jérôme Godbout
2018-11-26 16:20:21 UTC
Permalink
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-***@lists.qt-project.org> On Behalf Of Stanislas RENAN
Sent: November 24, 2018 3:18 AM
To: ***@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:***@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-***@lists.qt-project.org><mailto:interest-***@lists.qt-project.org> On Behalf Of Jérôme Godbout
Sent: November 20, 2018 7:54 PM
To: ***@qt-project.org<mailto:***@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:***@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:***@01D48579.4BBC84D0]<https://www.facebook.com/LesSolutionsAmotus/> [cid:***@01D48579.4BBC84D0] <https://www.linkedin.com/company/amotus-solutions/> [cid:***@01D48579.4BBC84D0] <https://twitter.com/AmotusSolutions> [cid:***@01D48579.4BBC84D0] <https://www.youtube.com/channel/UCoYpQgsmj1iJZyDjTQ3x8Ig>








_______________________________________________

Interest mailing list

***@lists.qt-project.org<mailto:***@lists.qt-project.org>

https://lists.qt-project.org/listinfo/interest
coroberti .
2018-11-26 19:00:43 UTC
Permalink
Hi,
It might be the firewall of the device that stops the incoming connections.

Kind regards,
Robert Iakobashvili
............................
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
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.
RENAN
*Sent:* November 24, 2018 3:18 AM
*Subject:* Re: [Interest] Qt Creator Samsung Android gdb can't connect
Hi,
Does run-as work on your devices ?
Best regards,
Stanislas RENAN
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
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.
*Sent:* November 20, 2018 7:54 PM
*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.
[image: 36E56279]
une compagnie
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
<https://www.facebook.com/LesSolutionsAmotus/>
<https://www.linkedin.com/company/amotus-solutions/>
<https://twitter.com/AmotusSolutions>
<https://www.youtube.com/channel/UCoYpQgsmj1iJZyDjTQ3x8Ig>
_______________________________________________
Interest mailing list
https://lists.qt-project.org/listinfo/interest
_______________________________________________
Interest mailing list
https://lists.qt-project.org/listinfo/interest
Jérôme Godbout
2018-11-26 19:08:39 UTC
Permalink
I don’t think I have access to Android firewall settings into the Android device, I might be wrong, but I don’t see any settings to do so.

P.S.: I pray for a true Linux phone one day


From: coroberti . <***@gmail.com>
Sent: November 26, 2018 2:01 PM
To: ***@lists.qt-project.org
Cc: JérÎme Godbout <***@amotus.ca>; qt-***@renan.org
Subject: Re: [Interest] Qt Creator Samsung Android gdb can't connect

Hi,
It might be the firewall of the device that stops the incoming connections.

Kind regards,
Robert Iakobashvili
............................


On Mon, Nov 26, 2018 at 8:57 PM JérÎme Godbout <***@amotus.ca<mailto:***@amotus.ca>> wrote:
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-***@lists.qt-project.org<mailto:interest-***@lists.qt-project.org>> On Behalf Of Stanislas RENAN
Sent: November 24, 2018 3:18 AM
To: ***@lists.qt-project.org<mailto:***@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:***@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-***@lists.qt-project.org><mailto:interest-***@lists.qt-project.org> On Behalf Of JérÎme Godbout
Sent: November 20, 2018 7:54 PM
To: ***@qt-project.org<mailto:***@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:***@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:***@01D48579.4BBC84D0]<https://www.facebook.com/LesSolutionsAmotus/> [cid:***@01D48579.4BBC84D0] <https://www.linkedin.com/company/amotus-solutions/> [cid:***@01D48579.4BBC84D0] <https://twitter.com/AmotusSolutions> [cid:***@01D48579.4BBC84D0] <https://www.youtube.com/channel/UCoYpQgsmj1iJZyDjTQ3x8Ig>







_______________________________________________

Interest mailing list

***@lists.qt-project.org<mailto:***@lists.qt-project.org>

https://lists.qt-project.org/listinfo/interest
_______________________________________________
Interest mailing list
***@lists.qt-project.org<mailto:***@lists.qt-project.org>
https://lists.qt-project.org/listinfo/interest
coroberti .
2018-11-26 19:13:12 UTC
Permalink
It might be that the device has some
"Enable Debugging" or "Allow debugging" in some "Developer Options/Section"
that opens the firewall at the right ports.

Kind regards,
Robert Iakobashvili
............................
Post by Jérôme Godbout
I don’t think I have access to Android firewall settings into the Android
device, I might be wrong, but I don’t see any settings to do so.
P.S.: I pray for a true Linux phone one day

*Sent:* November 26, 2018 2:01 PM
*Subject:* Re: [Interest] Qt Creator Samsung Android gdb can't connect
Hi,
It might be the firewall of the device that stops the incoming connections.
Kind regards,
Robert Iakobashvili
............................
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
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.
RENAN
*Sent:* November 24, 2018 3:18 AM
*Subject:* Re: [Interest] Qt Creator Samsung Android gdb can't connect
Hi,
Does run-as work on your devices ?
Best regards,
Stanislas RENAN
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
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.
*Sent:* November 20, 2018 7:54 PM
*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.
[image: 36E56279]
une compagnie
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
<https://www.facebook.com/LesSolutionsAmotus/>
<https://www.linkedin.com/company/amotus-solutions/>
<https://twitter.com/AmotusSolutions>
<https://www.youtube.com/channel/UCoYpQgsmj1iJZyDjTQ3x8Ig>
_______________________________________________
Interest mailing list
https://lists.qt-project.org/listinfo/interest
_______________________________________________
Interest mailing list
https://lists.qt-project.org/listinfo/interest
Jérôme Godbout
2018-11-26 21:19:40 UTC
Permalink
I have the USB debugging enabled, I don’t see any Firewall settings. I have uncheck the check application by USB port.

From: coroberti . <***@gmail.com>
Sent: November 26, 2018 2:13 PM
To: JérÎme Godbout <***@amotus.ca>
Cc: ***@lists.qt-project.org; qt-***@renan.org
Subject: Re: [Interest] Qt Creator Samsung Android gdb can't connect

It might be that the device has some
"Enable Debugging" or "Allow debugging" in some "Developer Options/Section"
that opens the firewall at the right ports.

Kind regards,
Robert Iakobashvili
............................


On Mon, Nov 26, 2018 at 9:08 PM JérÎme Godbout <***@amotus.ca<mailto:***@amotus.ca>> wrote:
I don’t think I have access to Android firewall settings into the Android device, I might be wrong, but I don’t see any settings to do so.

P.S.: I pray for a true Linux phone one day


From: coroberti . <***@gmail.com<mailto:***@gmail.com>>
Sent: November 26, 2018 2:01 PM
To: ***@lists.qt-project.org<mailto:***@lists.qt-project.org>
Cc: JérÎme Godbout <***@amotus.ca<mailto:***@amotus.ca>>; qt-***@renan.org<mailto:qt-***@renan.org>
Subject: Re: [Interest] Qt Creator Samsung Android gdb can't connect

Hi,
It might be the firewall of the device that stops the incoming connections.

Kind regards,
Robert Iakobashvili
............................


On Mon, Nov 26, 2018 at 8:57 PM JérÎme Godbout <***@amotus.ca<mailto:***@amotus.ca>> wrote:
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-***@lists.qt-project.org<mailto:interest-***@lists.qt-project.org>> On Behalf Of Stanislas RENAN
Sent: November 24, 2018 3:18 AM
To: ***@lists.qt-project.org<mailto:***@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:

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-***@lists.qt-project.org><mailto:interest-***@lists.qt-project.org> On Behalf Of JérÎme Godbout
Sent: November 20, 2018 7:54 PM
To: ***@qt-project.org<mailto:***@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.


une compagnie
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/>
<https://www.facebook.com/LesSolutionsAmotus/>


<https://www.facebook.com/LesSolutionsAmotus/>
<https://www.facebook.com/LesSolutionsAmotus/>
<https://www.facebook.com/LesSolutionsAmotus/>

_______________________________________________<https://www.facebook.com/LesSolutionsAmotus/>

Interest mailing list<https://www.facebook.com/LesSolutionsAmotus/>

***@lists.qt-project.org<https://www.facebook.com/LesSolutionsAmotus/>

https://lists.qt-project.org/listinfo/interest<https://www.facebook.com/LesSolutionsAmotus/>

_______________________________________________
Interest mailing list
***@lists.qt-project.org
https://lists.qt-project.org/listinfo/interest<https://www.facebook.com/LesSolutionsAmotus/>
Dmitriy Purgin
2018-11-26 20:25:46 UTC
Permalink
Post by Jérôme Godbout
P.S.: I pray for a true Linux phone one day

A bit off topic but if you're looking for a Linux phone, take a look at
Jolla's Sailfish OS. It's a true Linux system built on Qt.

Cheers
Dmitriy Purgin
Post by Jérôme Godbout
I don’t think I have access to Android firewall settings into the Android
device, I might be wrong, but I don’t see any settings to do so.
P.S.: I pray for a true Linux phone one day

*Sent:* November 26, 2018 2:01 PM
*Subject:* Re: [Interest] Qt Creator Samsung Android gdb can't connect
Hi,
It might be the firewall of the device that stops the incoming connections.
Kind regards,
Robert Iakobashvili
............................
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
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.
RENAN
*Sent:* November 24, 2018 3:18 AM
*Subject:* Re: [Interest] Qt Creator Samsung Android gdb can't connect
Hi,
Does run-as work on your devices ?
Best regards,
Stanislas RENAN
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
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.
*Sent:* November 20, 2018 7:54 PM
*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.
[image: 36E56279]
une compagnie
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
<https://www.facebook.com/LesSolutionsAmotus/>
<https://www.linkedin.com/company/amotus-solutions/>
<https://twitter.com/AmotusSolutions>
<https://www.youtube.com/channel/UCoYpQgsmj1iJZyDjTQ3x8Ig>
_______________________________________________
Interest mailing list
https://lists.qt-project.org/listinfo/interest
_______________________________________________
Interest mailing list
https://lists.qt-project.org/listinfo/interest
_______________________________________________
Interest mailing list
https://lists.qt-project.org/listinfo/interest
Jérôme Godbout
2018-11-26 21:10:30 UTC
Permalink
Nice to see something that finally emerge into this way, just hope the phone support get a little larger, the only real support seem to be Sony Xperia for now. But this is a foot in the right direction to finally get a real true open source and customizable phone OS. I will keep an eye on this, look promising. Thanks for the info!

From: Dmitriy Purgin <***@gmail.com>
Sent: November 26, 2018 3:26 PM
To: JérÎme Godbout <***@amotus.ca>
Cc: ***@gmail.com; ***@lists.qt-project.org
Subject: Re: [Interest] Qt Creator Samsung Android gdb can't connect
Post by Jérôme Godbout
P.S.: I pray for a true Linux phone one day

A bit off topic but if you're looking for a Linux phone, take a look at Jolla's Sailfish OS. It's a true Linux system built on Qt.

Cheers
Dmitriy Purgin


On Mon, Nov 26, 2018 at 9:23 PM JérÎme Godbout <***@amotus.ca<mailto:***@amotus.ca>> wrote:
I don’t think I have access to Android firewall settings into the Android device, I might be wrong, but I don’t see any settings to do so.

P.S.: I pray for a true Linux phone one day


From: coroberti . <***@gmail.com<mailto:***@gmail.com>>
Sent: November 26, 2018 2:01 PM
To: ***@lists.qt-project.org<mailto:***@lists.qt-project.org>
Cc: JérÎme Godbout <***@amotus.ca<mailto:***@amotus.ca>>; qt-***@renan.org<mailto:qt-***@renan.org>
Subject: Re: [Interest] Qt Creator Samsung Android gdb can't connect

Hi,
It might be the firewall of the device that stops the incoming connections.

Kind regards,
Robert Iakobashvili
............................


On Mon, Nov 26, 2018 at 8:57 PM JérÎme Godbout <***@amotus.ca<mailto:***@amotus.ca>> wrote:
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-***@lists.qt-project.org<mailto:interest-***@lists.qt-project.org>> On Behalf Of Stanislas RENAN
Sent: November 24, 2018 3:18 AM
To: ***@lists.qt-project.org<mailto:***@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:

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-***@lists.qt-project.org><mailto:interest-***@lists.qt-project.org> On Behalf Of JérÎme Godbout
Sent: November 20, 2018 7:54 PM
To: ***@qt-project.org<mailto:***@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.


une compagnie
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/>
<https://www.facebook.com/LesSolutionsAmotus/>


<https://www.facebook.com/LesSolutionsAmotus/>
<https://www.facebook.com/LesSolutionsAmotus/>
<https://www.facebook.com/LesSolutionsAmotus/>

_______________________________________________<https://www.facebook.com/LesSolutionsAmotus/>

Interest mailing list<https://www.facebook.com/LesSolutionsAmotus/>

***@lists.qt-project.org<https://www.facebook.com/LesSolutionsAmotus/>

https://lists.qt-project.org/listinfo/interest<https://www.facebook.com/LesSolutionsAmotus/>

_______________________________________________
Interest mailing list
***@lists.qt-project.org
https://lists.qt-project.org/listinfo/interest<https://www.facebook.com/LesSolutionsAmotus/>
_______________________________________________
Interest mailing list
***@lists.qt-project.org
https://lists.qt-project.org/listinfo/interest<https://www.facebook.com/LesSolutionsAmotus/>
André Pönitz
2018-11-26 19:39:21 UTC
Permalink
Post by Jérôme Godbout
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).
Windows->Views->Debugger Log, right pane, is the interesting thing whenever
there are problems with debugging.

Andre'
Jérôme Godbout
2018-11-26 21:17:03 UTC
Permalink
Ok, got it, sorry, did not knew this one existed (not sure it does help me, but might give some tips to someone with good knowledge on the flow):

On the first panel:
---------------------------------------
1373-file-exec-and-symbols "D:/Code/build/XXX-Android_for_armeabi_v7a_GCC_4_9_Qt_5_10_1_for_Android_armv7-Debug/app_process"
1374target extended-remote tcp:127.0.0.1:5039
1375python theDumper.exitGdb({"token":1375})
ERROR: UNEXPECTED STATE: EngineShutdownRequested WANTED: EngineSetupRequested IN C:\work\build\qt-creator\src\plugins\debugger\gdb\gdbengine.cpp:4659
Debugging has failed

On the second panel:
---------------------------------------
&"target extended-remote tcp:127.0.0.1:5039\n"
~"Remote debugging using tcp:127.0.0.1:5039\n"
&"Remote communication error. Target disconnected.: No error.\n"
dNOTE: INFERIOR EXITED
dState changed from EngineSetupRequested(1) to InferiorShutdownFinished(14)
dNOTE: INFERIOR EXITED
dState changed from EngineSetupRequested(1) to InferiorShutdownFinished(14) [master]
dState changed from InferiorShutdownFinished(14) to EngineShutdownRequested(15) [master]
dCALL: SHUTDOWN ENGINE
dState changed from EngineSetupOk(3) to EngineShutdownRequested(15)
dNOTE: ENGINE SHUTDOWN FINISHED
dState changed from EngineShutdownRequested(15) to EngineShutdownFinished(16)
dState changed from EngineShutdownFinished(16) to DebuggerFinished(17)
dState changed from InferiorShutdownFinished(14) to EngineShutdownRequested(15)
dINITIATE GDBENGINE SHUTDOWN, PROC STATE: 2
<1375python theDumper.exitGdb({"token":1375})
1374^error,msg="Remote communication error. Target disconnected.: No error."
eERROR: UNEXPECTED STATE: EngineShutdownRequested WANTED: EngineSetupRequested IN C:\work\build\qt-creator\src\plugins\debugger\gdb\gdbengine.cpp:4659
sFailed to start application: Connecting to remote server failed:
sRemote communication error. Target disconnected.: No error.
dINFERIOR START FAILED
dNOTE: ENGINE SETUP FAILED
dState changed from EngineShutdownRequested(15) to EngineSetupFailed(2)
dNOTE: ENGINE SETUP FAILED
dState changed from EngineShutdownRequested(15) to EngineSetupFailed(2) [master]
<Debugging has failed
dState changed from EngineSetupFailed(2) to DebuggerFinished(17) [master]
dState changed from EngineSetupFailed(2) to DebuggerFinished(17)

dQUIT DEBUGGER REQUESTED IN STATE 17
&"python theDumper.exitGdb({\"token\":1375})\n"
dGDB PROCESS FINISHED, status 0, exit code 0

-----Original Message-----
From: André Pönitz <***@t-online.de>
Sent: November 26, 2018 2:39 PM
To: Jérôme Godbout <***@amotus.ca>
Cc: Stanislas RENAN <qt-***@renan.org>; ***@lists.qt-project.org
Subject: Re: [Interest] Qt Creator Samsung Android gdb can't connect
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).
Windows->Views->Debugger Log, right pane, is the interesting thing
Windows->Views->whenever
there are problems with debugging.

Andre'
Loading...