This is the new way forward. Why is it better? Because it will ensure that remote debugging is just as good as local debugging. Otherwise remote debugging is something no one ever plays with and when people use it it doesn't work very well. It also means if something serious goes wrong, it can stop lldb itself from crashing and keeps LLDB out of the signal chain and many other things that can be beneficial when spawning child processes.
Is there a reason you want the old behavior back? Greg > On Jun 26, 2015, at 9:55 AM, Eugene Birukov <eugen...@hotmail.com> wrote: > > Hi, > > When I run lldb-4.6 that I apt-get on my Ubuntu 14.04 box, it runs as a > single process directly monitoring the target. When I run lldb-4.7 that I > built from sources, it starts lldb-server. Is this a legitimate policy > change or I miss some configuration option? I mean, is it possible to run > lldb-4.7 as a single process - the way 4.6 does? > > Thanks, > Eugene > _______________________________________________ > lldb-dev mailing list > lldb-dev@cs.uiuc.edu > http://lists.cs.uiuc.edu/mailman/listinfo/lldb-dev _______________________________________________ lldb-dev mailing list lldb-dev@cs.uiuc.edu http://lists.cs.uiuc.edu/mailman/listinfo/lldb-dev
