在Android SDK下调试framework

最新推荐文章于 2024-02-07 09:46:20 发布

此昵称已经存在吗

最新推荐文章于 2024-02-07 09:46:20 发布

阅读量3.5k

点赞数 1

分类专栏： android 文章标签： android image

本文链接：https://blog.csdn.net/superkris/article/details/7743790

版权

android 专栏收录该内容

22 篇文章 0 订阅

订阅专栏

通常情况下在eclipese的android SDK下新建一个工程(android4.0), 调试到framework里的函数的时候，在那里设置个断点，断点到了之后，按F5进行step into，

这时候会提示找不到framework的代码，因为工程是在android4.0下的AVD调试的，点击attach sources, 选择SDK目录下的sources\android14, 这时就可以进入framework的代码进行单步调试了，因为新的SDK没有2.3之前的代码，所以只能建4.0的。这样可以用SDK例子中的HOME来调试startActivity等的流程。

另外一种方式是用手里编译的framework代码调试，这时候需要新建工程，并把编译出来的framework的image替换点SDK中的image

建下面摘自google的说明。注意是先运行ddms的时候要选择里面要调试的进程，然后再调试framework。

如果手头有手机，就可以用手机代替模拟器，就不用每次编译模拟器了，直接编译手机版的image，用eclipse + 手机(用adb链接ddms) 就可以调试了。

http://source.android.com/source/using-eclipse.html

Using Eclipse

This document will help you set up the Eclipse IDE for Android platform development.

Note: if you are looking for information on how to use Eclipse to develop applications that run on Android, this is not the right page for you. You probably would find the Eclipse page on developer.android.com more useful.

Basic setup

First, it's important to make sure the regular Android development system is set up.

cd /path/to/android/root 
make

Important: You will still be using make to build the files you will actually run (in the emulator or on a device). You will be using Eclipse to edit files and verify that they compile, but when you want to run something you will need to make sure files are saved in Eclipse and run make in a shell. The Eclipse build is just for error checking.

Eclipse needs a list of directories to search for Java files. This is called the "Java Build Path" and can be set with the .classpath file. We have a sample version to start you off.

cd /path/to/android/root 
cp development/ide/eclipse/.classpath .
chmod u+w .classpath

Now edit that copy of .classpath, if necessary.

Increase Eclipse's Memory Settings

The Android project is large enough that Eclipse's Java VM sometimes runs out of memory while compiling it. Avoid this problem by editing the eclipse.ini file. On Apple OSX the eclipse.ini file is located at

/Applications/eclipse/Eclipse.app/Contents/MacOS/eclipse.ini

Memory-related defaults (as of Eclipse 3.4):

-Xms40m 
-Xmx256m 
-XX:MaxPermSize=256m

Recommended settings for Android development:

-Xms128m 
-Xmx512m 
-XX:MaxPermSize=256m

These settings set Eclipse's minimum Java heap size to 128MB, set the maximum Java heap size to 512MB, and keep the maximum permanent generation size at the default of 256MB.

Now start Eclipse:

eclipse

Now create a project for Android development:

If Eclipse asks you for a workspace location, choose the default.
If you have a "Welcome" screen, close it to reveal the Java perspective.
File > New > Java Project
Pick a project name, "android" or anything you like.
Select "Create project from existing source", enter the path to your Android root directory, and click Finish.
Wait while it sets up the project. (You'll see a subtle progress meter in the lower right corner.)

Once the project workspace is created, Eclipse should start building. In theory, it should build with no errors and you should be set to go. If necessary, uncheck and re-check Project Build Automatically to force a rebuild.

Note: Eclipse sometimes likes to add an import android.R statement at the top of your files that use resources, especially when you ask eclipse to sort or otherwise manage imports. This will cause your make to break. Look out for these erroneous import statements and delete them.

When You Sync

Every time you repo sync, or otherwise change files outside of Eclipse (especially the .classpath), you need to refresh Eclipse's view of things:

Window > Show View > Navigator
In the Navigator, right-click on the project name
Click Refresh in the context menu

Adding Apps to the Build Path

The default .classpath includes the source to the core system and a sample set of apps, but might not include the particular app you may want to work on. To add an app, you must add the app's source directory. To do this inside Eclipse:

Project > Properties
Select "Java Build Path" from the left-hand menu.
Choose the "Source" tab.
Click "Add Folder..."
Add your app's src directory.
Click OK.

When you're done, the "source folder" path in the list should look like

android/packages/apps/YOURAPP/src

Depending on which app(s) you include, you may also need to include othersrc/main/java directories under android/dalvik/libcore. Do this if you find you cannot build with the default set.

Eclipse formatting

You can import files in development/ide/eclipse to make Eclipse follow the Android style rules.

Select Window > Preferences > Java > Code Style.
Use Formatter > Import to import android-formatting.xml.
Organize Imports > Import to import android.importorder.

Debugging the emulator with Eclipse

You can also use eclipse to debug the emulator and step through code. First, start the emulator running:

cd /path/to/android/root 
. build/envsetup.sh 
lunch 1    
make       
emulator

If the emulator is running, you should see a picture of a phone.

In another shell, start DDMS (the Dalvik debug manager):

cd /path/to/android/root 
ddms

You should see a splufty debugging console.

Now, in eclipse, you can attach to the emulator:

Run > Open Debug Dialog...
Right-click "Remote Java Application", select "New".
Pick a name, i.e. "android-debug" or anything you like.
Set the "Project" to your project name.
Keep the Host set to "localhost", but change Port to 8700.
Click the "Debug" button and you should be all set.

Note that port 8700 is attached to whatever process is currently selected in the DDMS console, so you need to sure that DDMS has selected the process you want to debug.

You may need to open the Debug perspective (next to the "Java" perspective icon in the upper-right, click the small "Open Perspective" icon and select "Debug"). Once you do, you should see a list of threads; if you select one and break it (by clicking the "pause" icon), it should show the stack trace, source file, and line where execution is at. Breakpoints and whatnot should all work.

Bonus material

Replace Ctrl with the Apple key on Mac.

shortcut	function
Ctrl-Shift-o	Organize imports
Ctrl-Shift-t	load class by name
Ctrl-Shift-r	load non-class resource by name
Ctrl-1	quick fix
Ctrl-e	Recently viewed files
Ctrl-space	auto complete
Shift-Alt-r	refactor:rename
Shift-Alt-v	refactor:move