That't interesting. Where you able to simulate the error seen on the bots by inserting a sleep() unto the debugged program?
-- adrian > On Aug 10, 2018, at 5:06 PM, Александр Поляков <[email protected]> wrote: > > It seems that lldb-mi in such a situation just hangs: > > build/bin/lldb-mi --synchronous bash > (gdb) > -file-exec-and-symbols "bash" > ^done > (gdb) > =library-loaded,id="/bin/bash",target-name="/bin/bash",host-name="/bin/bash",symbols-loaded="0",loaded_addr="-",size="0" > -exec-run > ^C^C > exit > > It doesn't react to Ctrl+C and exit command. > > сб, 11 авг. 2018 г. в 2:54, Adrian Prantl <[email protected] > <mailto:[email protected]>>: > > >> On Aug 10, 2018, at 4:50 PM, Александр Поляков <[email protected] >> <mailto:[email protected]>> wrote: >> >> One important question: what do you mean talking about "block"? Does it mean >> that SBTarget::Launch blocks the process and the user can't continue working >> with this process until it stops? > > Pretty much. The same way as the interactive (lldb) command line interface > behaves: You enter "run" and you won't get a prompt again until the process > stops. I'm imagining (but haven't verified) that synchronous mode behaves > like that. > > -- adrian > > > > -- > Alexander
_______________________________________________ lldb-dev mailing list [email protected] http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
