[lldb-dev] LLDB for Android initiative

[Todd Fiala]

>  it might make sense to only use it as a port forwarder and go with an
lldb-platform on the device side and just stick with that.  I'll have a
deeper look at that once I get Android gdbserver (or equivalent) working.

It's very likely I'll need to base lldb-platform entirely around adb now
that I think about it.  adb activity is more or less the security
gatekeeper - if a user doesn't want a device to be debugged, it can prevent
adb from attaching to it.  I doubt I'd be able to get a useful
lldb-platform exe on the device with the right permissions for a non-rooted
build (i.e. a standard device image).  So an lldb-platform that builds
around adb on Android is likely going to be the way for me to at least
start.  This may require changing adb in some cases depending on exactly
what lldb-platform requires.

Andy - I'll be looking at your patch starting today.  I hit my first crash
in lldb on connecting to a stock android gdbserver against a Nexus 10
yesterday doing nothing other than attempting to connect :-)


On Wed, Nov 20, 2013 at 2:19 PM, Todd Fiala <tfiala at google.com> wrote:

> >
>> > There is probably some amount of overlap in lldb-platform and what we
>> currently do with adb (Android Debug Bridge).  Eventually I'll need to
>> figure out what makes sense to speed up the compile/deploy/debug/fix cycle.
>>
>> You can make a new platform named "remote-andriod" that can talk to adb,
>> and just skip using the "lldb-platform" binary. Anything that is missing in
>> that we need in the lldb_private::Platform class could then be added to
>> adb, and if we are missing anything in the lldb_private::Platform compared
>> to adb we could add to the platform API. How do you communicate with adb?
>> Sockets?
>>
>> ADB runs on the host/local side, and it knows how to forward ports to
> devices (typically over USB).  So, we talk to the local ADB port that then
> forwards communication to the actual device.  I'll need to have a look at
> the guts of it - it might make sense to only use it as a port forwarder and
> go with an lldb-platform on the device side and just stick with that.  I'll
> have a deeper look at that once I get Android gdbserver (or equivalent)
> working.
>
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/lldb-dev/attachments/20131122/df85e65d/attachment.html>