failed to get reply to handshake packet (Android studio 2.4 preview 5, os: macOS Sierra 10.12.4 ) not debugging ndk project

2,223 views
Skip to first unread message

Сергей Лоскутников

unread,
Apr 8, 2017, 6:46:25 PM4/8/17
to android-ndk
  I have a simple android project with ndk elements. The project does not start, because it has errors (more precisely  in the place where the program reaches AAssetManager_openTo understand the reason, I want to use the debugger Android studio. But when I launch it, it will load the application, think a bit and write the following error: failed to get reply to handshake packet. I have already read the tips to turn it off, reinstall and restart adb kill-server, adb start-server; not working. I have a question, can anyone come across and know what to do about it. Thank you in advance. ndk version 15.0.836...

 all mistakes 
failed to get reply to handshake packet
com.jetbrains.cidr.execution.debugger.backend.lldb.LLDBDriverException: failed to get reply to handshake packet
at com.jetbrains.cidr.execution.debugger.backend.lldb.LLDBDriver$ThrowIfNotValid.throwIfNeeded(LLDBDriver.java:143)
at com.android.tools.ndk.run.lldb.AndroidLLDBDriver.connectPlatform(AndroidLLDBDriver.java:293)
at com.android.tools.ndk.run.lldb.AndroidLLDBDriver.loadForLaunch(AndroidLLDBDriver.java:143)
at com.android.tools.ndk.run.lldb.AndroidLLDBDriver.loadForAttach(AndroidLLDBDriver.java:184)
at com.android.tools.ndk.run.AndroidNativeAppDebugProcess.prepareTarget(AndroidNativeAppDebugProcess.java:87)
at com.android.tools.ndk.run.AndroidNativeDebugProcess.doStart(AndroidNativeDebugProcess.java:113)
at com.jetbrains.cidr.execution.debugger.CidrDebugProcess$3.run(CidrDebugProcess.java:307)
at com.jetbrains.cidr.execution.debugger.CidrDebugProcess$MyCommandProcessor.consume(CidrDebugProcess.java:724)
at com.jetbrains.cidr.execution.debugger.CidrDebugProcess$MyCommandProcessor.consume(CidrDebugProcess.java:714)
at com.intellij.util.concurrency.QueueProcessor.lambda$null$0(QueueProcessor.java:106)
at com.intellij.util.concurrency.QueueProcessor.runSafely(QueueProcessor.java:223)
at com.intellij.util.concurrency.QueueProcessor.lambda$wrappingProcessor$1(QueueProcessor.java:106)
at com.intellij.util.concurrency.QueueProcessor.lambda$null$2(QueueProcessor.java:203)
at com.intellij.util.concurrency.QueueProcessor.runSafely(QueueProcessor.java:223)
at com.intellij.util.concurrency.QueueProcessor.lambda$startProcessing$3(QueueProcessor.java:203)
at com.intellij.openapi.application.impl.ApplicationImpl$2.run(ApplicationImpl.java:334)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
 

vishnu...@acsiatech.com

unread,
Sep 7, 2018, 3:49:12 AM9/7/18
to android-ndk
For me the issue got resolved, when I uninstalled the application and re-installed it. Did you tried that?
Reply all
Reply to author
Forward
0 new messages