> On Oct 18, 2016, at 10:14 PM, Chunseok Lee via lldb-dev
> <lldb-dev@lists.llvm.org> wrote:
>
> I have noticed that lldb-mi stopped after executing "-target-select remote".
> My execution step is like:
> ---------------------------------------------
> $ lldb-server g --platform=remote-linux "*:1234"
>
> $ lldb-mi
> (gdb)
> -file-exec-and-symbols /home/twoflower/a.out
> (gdb)
> -target-select remote localhost:1234
> .....
> (gdb)
> *stopped,reason="signal-received",signal-name="SIGSTOP",signal-meaning="Stop",frame={level="0",addr="0x00007f4bdf53e2d0",func="??",file="??",fullname="??",line="-1"},thread-id="1",stopped-threads="all"
> -------------------------------------------------
>
> In my project, I dont want to stop there.
> Where is a good point to investigate the code triggering SIGSTOP ?
I believe that many systems halt the process when you attach to it, so this is
normal. Just continue using normal debugger commands. This can all be done from
your IDE.
Greg
>
>
> BR,
> Chunseok Lee
>
> --
> Where Do We come from? What Are We? Where Are We Going?
> _______________________________________________
> lldb-dev mailing list
> lldb-dev@lists.llvm.org
> http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
_______________________________________________
lldb-dev mailing list
lldb-dev@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
