<html><head><meta http-equiv="Content-Type" content="text/html; charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">lldb-server claims it doesn't support it:<div class=""><br class=""></div><div class=""><div class="">lldb < 48> send packet: $vAttachWait;6c616e677365727665722d7377696674#d6</div><div class="">lldb < 4> read packet: $#00</div><div class=""><br class=""></div><div class=""><br class=""></div><div class="">Returning the empty packet ("$#00") means it is not supported, but we really should give a better error message than this. </div><div class=""><br class=""></div><div class="">It isn't that hard to implement. It would be easy to copy the code that is in debugserver in DNB.cpp in the <span style="font-size: 11px; background-color: rgb(255, 255, 255);" class="">DNBProcessAttachWait function. Most of it is probably posix style stuff. </span></div><div class=""><span style="font-size: 11px; background-color: rgb(255, 255, 255);" class=""><br class=""></span></div><div class=""><span style="font-size: 11px; background-color: rgb(255, 255, 255);" class="">So two issues here:</span></div><div class=""><span style="font-size: 11px; background-color: rgb(255, 255, 255);" class="">1 - we need a better error message when vAttachWait returns unsupported</span></div><div class=""><span style="font-size: 11px; background-color: rgb(255, 255, 255);" class="">2 - fix lldb-server to support vAttachWait</span></div><div class=""><br class=""></div><div class="">Greg</div><div class=""><br class=""></div><div><br class=""><blockquote type="cite" class=""><div class="">On May 31, 2018, at 11:04 AM, Ryan Lovelett <<a href="mailto:ryan@lovelett.me" class="">ryan@lovelett.me</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div class=""><blockquote type="cite" class="">It might be a lldb-server issue?<br class=""></blockquote><br class="">How would one go about determining this?<br class=""><br class="">(lldb) log enable -f /tmp/packates.txt gdb-remote packets<br class="">(lldb) process attach --name "<name>" --waitfor<br class="">error: attach failed: lost connection<br class=""><br class="">Attached the log output. Maybe it'll make more sense to you than me.<br class=""><br class="">That escalated quickly. So I've read through that log. I found something that says $qVAttachOrWaitSupported#38 with the following response being $#00. Perhaps I'm reading too much but is it that it's reporting that it is not supported?<br class=""><br class="">Does lldb-server need to be compiled in a certain way to add support for attach wait?<br class=""><br class="">On Thu, May 31, 2018, at 1:49 PM, Greg Clayton wrote:<br class=""><blockquote type="cite" class="">Try enabling logging with:<br class=""><br class="">(lldb) log enable -f /tmp/packets.txt gdb-remote packets<br class=""><br class="">And the try the attach. It might be a lldb-server issue?<br class=""><br class=""><blockquote type="cite" class="">On May 31, 2018, at 9:02 AM, Ryan Lovelett via lldb-dev <<a href="mailto:lldb-dev@lists.llvm.org" class="">lldb-dev@lists.llvm.org</a>> wrote:<br class=""><br class="">I am attempting to use: process attach --name "<name>" --waitfor<br class=""><br class="">The problem is that it immediately returns error: attach failed: lost connection.<br class=""><br class="">Is this something I can troubleshoot further? Or is this not supported on Linux?<br class=""><br class="">-- <br class=""> Ryan Lovelett<br class="">_______________________________________________<br class="">lldb-dev mailing list<br class=""><a href="mailto:lldb-dev@lists.llvm.org" class="">lldb-dev@lists.llvm.org</a><br class="">http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev<br class=""></blockquote><br class=""></blockquote><span id="cid:1527789439.1264405.a53eb3815d54e81efc286035ccdbcf075e45675c.11CDD911@content.messagingengine.com"><packates.txt></span></div></div></blockquote></div><br class=""></div></body></html>