<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">You need to send some sort of continue through the GDB remote interface. The only way to get a $T packet back is in response to a "?" packet or to a "vCont" or other continue or step packet.<div class=""><br class=""><div><blockquote type="cite" class=""><div class="">On Aug 22, 2017, at 2:30 PM, Vadim Chugunov <<a href="mailto:vadimcn@gmail.com" class="">vadimcn@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class="">It does send '$T05...' in response, but it looks like lldb does not analyze responses to manually sent packets.</div><div class="gmail_extra"><br class=""><div class="gmail_quote">On Mon, Aug 21, 2017 at 1:02 PM, Greg Clayton <span dir="ltr" class=""><<a href="mailto:clayborg@gmail.com" target="_blank" class="">clayborg@gmail.com</a>></span> wrote:<br class=""><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">If you do a reverse step it actually should send a process resumed and a process stopped event.<br class="">
<br class="">
> On Aug 18, 2017, at 7:19 PM, Vadim via lldb-dev <<a href="mailto:lldb-dev@lists.llvm.org" class="">lldb-dev@lists.llvm.org</a>> wrote:<br class="">
><br class="">
> I'm trying to reverse-step. So I think I'd need to refresh all thread states?<br class="">
><br class="">
>> On Aug 18, 2017, at 4:50 PM, Jim Ingham <<a href="mailto:jingham@apple.com" class="">jingham@apple.com</a>> wrote:<br class="">
>><br class="">
>> No, there hasn't been a need for this.<br class="">
>><br class="">
>> What commands are you planning to send? Or equivalently, how much state are you expecting to change?<br class="">
>><br class="">
>> Jim<br class="">
>><br class="">
>>> On Aug 18, 2017, at 4:36 PM, Vadim Chugunov via lldb-dev <<a href="mailto:lldb-dev@lists.llvm.org" class="">lldb-dev@lists.llvm.org</a>> wrote:<br class="">
>>><br class="">
>>> Hi,<br class="">
>>> Is there any way to force lldb to refresh it's internal record of debuggee process state (as if it had just received a stop event)? I want to send a custom command to remote gdb process stub (via `process plugin packet send`). This works, but if the command alters debuggee state, lldb won't know about it.<br class="">
>>> ______________________________<wbr 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="">
>>> <a href="http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev" rel="noreferrer" target="_blank" class="">http://lists.llvm.org/cgi-bin/<wbr class="">mailman/listinfo/lldb-dev</a><br class="">
>><br class="">
> ______________________________<wbr 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="">
> <a href="http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev" rel="noreferrer" target="_blank" class="">http://lists.llvm.org/cgi-bin/<wbr class="">mailman/listinfo/lldb-dev</a><br class="">
<br class="">
</blockquote></div><br class=""></div>
</div></blockquote></div><br class=""></div></body></html>