Note that the part of lldb that needs to be apple code-signed to be convenient for use is only the "debugserver" tool which lives in LLDB.framework/Contents/Resources. So if you really need to distribute something with lldb libraries you have built yourself, you can just grab the debugserver from an official build and use that. lldb is expected to be able to work with a variety of debug servers, so that shouldn't cause any problems (short of bugs of course...)
Jim > On Dec 1, 2014, at 2:27 AM, René J.V. Bertin <rjvber...@gmail.com> wrote: > > On Monday December 01 2014 10:16:32 Colin Riley wrote: >> Just to quickly butt in; >> >> The lldb-mi driver can be found in tools/lldb-mi and at works with >> eclipse debugging remote hosts. There are a few contributing to it now, >> so hopefully more features are incoming. > > Thanks! > > I was going to reply that I'd go have a look and then say something about > Apple ... and then realised that Apple's sandboxing on OS X is probably going > to oblige me to use whatever they deign to provide. My experience with FOSS > gdb (which I managed to get to work on 10.6.8 but not on 10.9) doesn't make > me very enthusiastic to experiment with other options ... > I'll try the Python and simple C++ examples though, who knows if the fact > they use an Apple-sanctioned library is enough to open the (task)gate(d)s to > other processes' internals :) > > R. > _______________________________________________ > 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
