Re: debugger at wrong line when stepping through android methods

[Kristopher Micinski]

1) I don't think the point of providing the sources is to allow
developers to debug their apps, that's a nice byproduct but the main
reason the source is released is to allow people to build custom
platforms, etc..
2) You're absolutely certain that you have the right version of the
sources for the API level you're on?
3) I agree having sources is nice and fun, but you shouldn't really
need to rely on them for debugging unless you're doing platform
development. (You never mentioned this.) Occasionally if I have a
problem that's really tough, I'd dig through platform sources, but for
the vast majority of cases I don't need it..

kris

On Thu, Aug 9, 2012 at 9:22 AM, darKoram <solarmobi...@gmail.com> wrote:
> After downloading sources from the site below, DDB will step into android
> methods, but most of the time, the line numbers are WAY off. So much so
> that it's hardly useful at all.
>
> I've had this problem since starting dev with android, and it really seems
> to defeat the usefulness of coding in an opensource framework. I'm
> developing in Eclipse in ubuntu. Only a few android targets have sources
> available for download via the sdk manager, so i have to:
>
> Get the Android source code (install repo, repo init, repo sync)
>
> Move all Java sources into a "sources" subdirectory of the Android SDK
>
> Some android methods are still not found. Which may have a solution in
> re-organizing the file structure to be in line with java package naming
> convention ala
> http://blog.michael-forster.de/2008/12/view-android-source-code-in-eclipse.html
>
> I haven't tried this, but it's not related to the line-number mismatch
> problem.
>
> I presume the problem is that the source published in 1. is slightly
> different from the 'blessed" builds that become android-n.
> I could build the sdk and platform tools from the sources at 1. so it
> matches the source i have, but I anticipate that that would create problems
> at deployment time, as my targets wouldn't exactly match the real Google
> release targets. What I really want is sources that match the release
> builds. I can provide specific examples of mismatch, but i presume this is
> a know problem as classes involved are as prominent as Activity.java (in my
> case for android 15).
>
> It would be soooo much nicer if google would just have sources available via
> the sdk manager for every target. I've spent days on this one, so it's
> gotta be a real drag on developer productivity en mass.
>
> darKoram
>
>
>
> --
> You received this message because you are subscribed to the Google Groups
> "android-platform" group.
> To view this discussion on the web visit
> https://groups.google.com/d/msg/android-platform/-/lUP5zugqlWwJ.
> To post to this group, send email to android-...@googlegroups.com.
> To unsubscribe from this group, send email to
> android-platfo...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/android-platform?hl=en.

[Ubuntu guy]

I used to have similar problems when i synced the code base from head
of master branch.
So i use the specific release tag info documented at
https://android.googlesource.com/platform/manifest.

On Aug 9, 6:22 am, darKoram <solarmobiletrail...@gmail.com> wrote:
> After downloading sources from the site below, DDB will step into android
> methods, but most of the time, the line numbers are WAY off.  So much so
> that it's hardly useful at all.
>
> I've had this problem since starting dev with android, and it really seems
> to defeat the usefulness of coding in an opensource framework.  I'm
> developing in Eclipse in ubuntu.  Only a few android targets have sources
> available for download via the sdk manager, so i have to:
>

>    1.
>
>    Get the Android source code <http://source.android.com/download/> (install
>    repo <http://source.android.com/download/using-repo#TOC-Task-reference>,
>    repo init, repo sync)
>    2.

>
>    Move all Java sources into a "sources" subdirectory of the Android SDK
>
> Some android methods are still not found.  Which may have a solution in
> re-organizing the file structure to be in line with java package naming

> convention ala  http://blog.michael-forster.de/2008/12/view-android-source-code-in-ec...