Re: [android-building] ICS debug build

195 views
Skip to first unread message

Jean-Baptiste Queru

unread,
Jun 4, 2013, 11:25:46 PM6/4/13
to android-...@googlegroups.com
I'm not sure that this is used any more. This goes back to the time when some of Android could be run in a linux desktop process in order to run valgrind, but we now run valgrind natively in Android.

You might be looking for build variants instead, especially -eng (instead of -user or -userdebug), but I'm not sure that'll do what you want.

JBQ


On Tue, Jun 4, 2013 at 8:12 PM, Vikram <vikram....@gmail.com> wrote:

I am trying to add a new system service to ICS. I followed steps outlined here:

https://groups.google.com/forum/?fromgroups=#!topic/android-porting/Abo8kZUbiKw

and booted my device, only to have it go into an "untracked pid nnnn exited" loop. Fortunately there was some debug info available, namely a JNIHelp error that said "Native registration unable to find class". That helped me fix an obvious bug in the java source for my service; I then rebuilt and rebooted with the new rootfs. The device still goes into the same "untracked pid exited" loop. Unfortunately, this time there is no additional debug info on the console.

I figured a debug build might yield more verbose messages, and tried building with TARGET_BUILD_TYPE=debug. However, the debug build output seems crippled- more than half the jars under system/framework are missing, including those for am/pm/services. I had assumed that the debug build ought to be the same as a release build, except with verbose logging. Is that not the case?

I tried doing an "mm TARGET_BUILD_TYPE=debug" under frameworks/base/services/java, and make fails with the following:


make: *** No rule to make target `out/debug/target/common/obj/JAVA_LIBRARIES/android.policy_intermediates/javalib.jar', needed by `out/debug/target/common/obj/JAVA_LIBRARIES/services_intermediates/classes-full-debug.jar'.  Stop.

How do I do the debug build? If that is not possible, what are my options to get more visibility into what's going on? From the comments in system/core/include/cutils/log.h, apparently I can "#define LOG_NDEBUG 0" at the top of a source file to get verbose logging, but I'm not sure I am familiar enough with AOSP yet to judiciously select a set of files do this.

I'd appreciate any pointers on this. Thanks!

-Vikram

--
--
You received this message because you are subscribed to the "Android Building" mailing list.
To post to this group, send email to android-...@googlegroups.com
To unsubscribe from this group, send email to
android-buildi...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-building?hl=en
 
---
You received this message because you are subscribed to the Google Groups "Android Building" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-buildi...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 



--
Jean-Baptiste M. "JBQ" Queru
Technical Lead, Android Open Source Project, Google.

Questions sent directly to me that have no reason for being private will likely get ignored or forwarded to a public forum with no further warning.
Reply all
Reply to author
Forward
0 new messages