On 25.10.2016 01:43, Saleem Abdulrasool via lldb-dev wrote: > On Mon, Oct 24, 2016 at 11:38 AM, Ed Maste via lldb-commits > <lldb-comm...@lists.llvm.org <mailto:lldb-comm...@lists.llvm.org>> wrote: > > On 24 October 2016 at 06:26, Pavel Labath <lab...@google.com > <mailto:lab...@google.com>> wrote: > > > > It's not my place to tell you how to work, but I'd recommend a > > different approach to this. If you base your work on the current > > FreeBSD in-process plugin, then when you get around to actually > > implementing remote support, you will find that you will have to > > rewrite most of what you have already done to work with lldb-server, > > as it uses completely different class hierarchies and everything. I'd > > recommend starting with lldb-server right away. It's going to be a bit > > more work as (I assume) freebsd implementation is closer to what you > > need than linux, but I think it will save you time in the long run. I > > can help you with factoring out any linux-specific code that you > > encounter. > > I definitely second the approach Pavel suggests here, and am happy to > work with others on refactoring the Linux lldb-server so that we can > get it to support both FreeBSD and NetBSD at the same time. > > A direct port of the current FreeBSD support probably would result in > a basic level of support running sooner, but that work would be > largely thrown away in a future migration to lldb-server. > > > Just to throw out another option: DS2 (DebugServer2) at > http://github.com/facebook/ds2 may be another option to getting remote > debugging working. It already has basic BSD support, so adding NetBSD > support shouldn't be too difficult. >
It's an interesting program, but for now I would leave it for later as it's out of LLDB.
signature.asc
Description: OpenPGP digital signature
_______________________________________________ lldb-dev mailing list lldb-dev@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
