Hello.
Please review this proposal for title and abstract. The rules are:
*Provide a 150 word abstract that briefly summarizes your proposal. It should be split into two paragraphs: the first should be a brief summary of your proposal, including key highlights and relevance; the second should describe who your audience is, what they can expect and the level of technical expertise required*
When commenting - please consider that I only have one more word available :) Also consider that commercial plugs are always rejected.
--------- *Title:* Painless debugging of native code in Android-based devices
*Abstract:* Advanced Android apps may use native C/C++ code called trough the Java Native Interface. Such Android apps are made possible by the Android Native Development Kit. The Eclipse-based Android IDE is great for creating Java apps, but for debugging native code on a physical ARM-based device there are many obstacles. This talk will show how debugging can be made less painful by using the DS-5 Community Edition Eclipse plugin. Two debug sessions will be walked trough. The first example shows debugging a shared library belonging to a stand-alone app. The second example shows how to debug a system service in a Linaro AOSP-based Android system using real-time profiling to visualize activity in the device.
The presentation is aimed at developers who are not Linux gurus, but are entering the Linux community trough Android. That can e.g. be former Java developers or former RTOS developers switching to Android in their embedded devices. ---------
CFP deadline is on Friday, so please send me feedback ASAP.
BR, Tony
+ Vinod. Please note that Vinod is back from vacation on the 6th of Jan.
On 4 January 2012 18:54, Tony Mansson tony.mansson@linaro.org wrote:
Hello.
Please review this proposal for title and abstract. The rules are:
Provide a 150 word abstract that briefly summarizes your proposal. It should be split into two paragraphs: the first should be a brief summary of your proposal, including key highlights and relevance; the second should describe who your audience is, what they can expect and the level of technical expertise required
When commenting - please consider that I only have one more word available :) Also consider that commercial plugs are always rejected.
Title: Painless debugging of native code in Android-based devices
Abstract: Advanced Android apps may use native C/C++ code called trough the Java Native Interface. Such Android apps are made possible by the Android Native Development Kit. The Eclipse-based Android IDE is great for creating Java apps, but for debugging native code on a physical ARM-based device there are many obstacles. This talk will show how debugging can be made less painful by using the DS-5 Community Edition Eclipse plugin. Two debug sessions will be walked trough. The first example shows debugging a shared library belonging to a stand-alone app. The second example shows how to debug a system service in a Linaro AOSP-based Android system using real-time profiling to visualize activity in the device.
The presentation is aimed at developers who are not Linux gurus, but are entering the Linux community trough Android. That can e.g. be former Java developers or former RTOS developers switching to Android in their embedded devices.
CFP deadline is on Friday, so please send me feedback ASAP.
BR, Tony
linaro-android mailing list linaro-android@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-android
linaro-android@lists.linaro.org
-
anmar.oueja＠linaro.org -
Tony Mansson