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 <[email protected]>
Sent: November 26, 2018 2:39 PM
To: Jérôme Godbout <[email protected]>
Cc: Stanislas RENAN <[email protected]>; [email protected]
Subject: Re: [Interest] Qt Creator Samsung Android gdb can't connect
On Mon, Nov 26, 2018 at 04:20:21PM +0000, Jérôme Godbout 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).
Windows->Views->Debugger Log, right pane, is the interesting thing
Windows->Views->whenever
there are problems with debugging.
Andre'
_______________________________________________
Interest mailing list
[email protected]
https://lists.qt-project.org/listinfo/interest
