[lldb-dev] Failing LIT-based lldb-mi tests

[Александр Поляков via lldb-dev]

AFAIK, there is no mechanism in lldb-mi to distinguish a command that
expects a frame, so we need to modify each command manually. Am I right?
If so, I found the Process::WaitForProcessToStop method which we can add to
SB API and use in lldb-mi.

сб, 11 авг. 2018 г. в 0:50, Adrian Prantl <aprantl at apple.com>:

> [adding lldb-dev back to the conversation]
>
> > On Aug 10, 2018, at 2:37 PM, Adrian Prantl <aprantl at apple.com> wrote:
> >
> >
> >
> >> On Aug 10, 2018, at 2:25 PM, Александр Поляков <polyakov.alx at gmail.com>
> wrote:
> >>
> >> I didn't check this yet. lldb-mi already runs LIT test in the
> --synchronous mode and the tests keep failing.
> >>
> >
> > Yes, that's why I said this:
> >
> >
> >>> пт, 10 авг. 2018 г. в 23:57, Adrian Prantl <aprantl at apple.com>:
> >>>
> >>> Before we continue to discuss -wait-for-breakpoint; where you actually
> able to verify my suspicion that that is what is happening on the bots?
> Fred suggested to me offline today that in synchronous mode, perhaps
> -exec-* should be waiting for the process to be stopped, which would also
> sound like a reasonable and less invasive solution to the problem.
> >>>
> >>
> >
> > Instead of adding a new command to wait for the process to be stopped we
> might be able to just wait for the process to be stopped if in synchronous
> mode and we are running any commands that expect a frame (such as -exec-*).
> >
> > -- adrian
>
>

-- 
Alexander
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/lldb-dev/attachments/20180811/e1c4800f/attachment.html>