Process exited with status -1 (unable to attach) Process finished with exit code 0
已回答
I am able to run code, but unable to debug. When I try to debug, I get the error:
process exited with status -1 (unable to attach)
Process finished with exit code
请先登录再写评论。
@Cameronsanders do you use bundled LLDB or custom? What OS and CLion's version do you have? Please also enable debugger logging as described here, reproduce the issue and send the resulting idea.log file to clion-support at jetbrains.com. Thanks.
Hi!
Do you have any update on this issue?
It seems I stumbled upon the same one after upgrading to Mac OS High Sierra (10.13.3).
I'm using CLion 2017.3.4 with built in LLDB.
It can't attach to any process. Apple LLDB installed with XCode looks good, though.
Stacktrace from debugger log looks as follows:
018-03-28 13:20:49,572 [1776435] DEBUG - brains.cidr.execution.debugger - [protobuf client 6] 1392 res:launch {common_response {
is_valid: false
error_message: "process exited with status -1 (unable to attach)"
}
}
2018-03-28 13:20:49,573 [1776436] DEBUG - brains.cidr.execution.debugger -
com.jetbrains.cidr.execution.debugger.backend.lldb.LLDBDriverException: process exited with status -1 (unable to attach)
at com.jetbrains.cidr.execution.debugger.backend.lldb.LLDBDriver$ThrowIfNotValid.throwIfNeeded(LLDBDriver.java:133)
at com.jetbrains.cidr.execution.debugger.backend.lldb.LLDBDriver.a(LLDBDriver.java:476)
at com.jetbrains.cidr.execution.debugger.backend.lldb.LLDBDriver.access$700(LLDBDriver.java:49)
at com.jetbrains.cidr.execution.debugger.backend.lldb.LLDBDriver$5.startImpl(LLDBDriver.java:290)
at com.jetbrains.cidr.execution.debugger.backend.DebuggerDriver$Inferior.start(DebuggerDriver.java:665)
at com.jetbrains.cidr.execution.debugger.CidrDebugProcess.doStartTarget(CidrDebugProcess.java:441)
at com.jetbrains.cidr.execution.debugger.CidrDebugProcess.b(CidrDebugProcess.java:434)
at com.jetbrains.cidr.execution.debugger.CidrDebugProcess$MyCommandProcessor.consume(CidrDebugProcess.java:697)
at com.jetbrains.cidr.execution.debugger.CidrDebugProcess$MyCommandProcessor.consume(CidrDebugProcess.java:687)
at com.intellij.util.concurrency.QueueProcessor.lambda$null$0(QueueProcessor.java:93)
at com.intellij.util.concurrency.QueueProcessor.runSafely(QueueProcessor.java:246)
at com.intellij.util.concurrency.QueueProcessor.lambda$wrappingProcessor$1(QueueProcessor.java:93)
at com.intellij.util.concurrency.QueueProcessor.lambda$null$3(QueueProcessor.java:226)
at com.intellij.util.concurrency.QueueProcessor.runSafely(QueueProcessor.java:246)
at com.intellij.util.concurrency.QueueProcessor.lambda$startProcessing$4(QueueProcessor.java:226)
at com.intellij.openapi.application.impl.ApplicationImpl$1.run(ApplicationImpl.java:315)
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)
2018-03-28 13:20:49,577 [1776440] DEBUG - brains.cidr.execution.debugger - [protobuf client 6] 1396 req(7): kill {
}
2018-03-28 13:20:49,579 [1776442] DEBUG - brains.cidr.execution.debugger - [protobuf client 6] 1398 res:kill {
common_response {
is_valid: true
}
}