Difference between revisions of "Tracking Library Use"
| Line 3: | Line 3: | ||
1. Find library in question. | 1. Find library in question. | ||
| − | [[File:onConfigurationChanged.png| | + | [[File:onConfigurationChanged.png|600px]] |
2. If concerned with particular methods/fields, use call-step/dataflow-step. | 2. If concerned with particular methods/fields, use call-step/dataflow-step. | ||
| Line 21: | Line 21: | ||
[[File:LibraryFiltered.png|500px]] | [[File:LibraryFiltered.png|500px]] | ||
| − | 6. Double-click on other calls to examine them in the source code. Let's look at the other method in our class that calls <code>android.content.pm</code> first. Double-clicking the method takes us to the method declaration, or double-clicking the | + | 6. Double-click on other calls to examine them in the source code. Let's look at the other method in our class that calls <code>android.content.pm</code> first. Double-clicking the method takes us to the method declaration, or double-clicking the edge directly highlights the line where the library is called. |
[[File:ConfigureOrientation.png|700px]] | [[File:ConfigureOrientation.png|700px]] | ||
| | ||
[[File:FollowEdge.png|300px]] | [[File:FollowEdge.png|300px]] | ||
| + | |||
| + | 7. Next, we can see that the only other class accessing the library in question has multiple reads from one method. | ||
| + | |||
| + | [[File:TerminalViewLibraryAccess.png|500px]] | ||
Revision as of 22:08, 26 April 2015
"Where is this library being used?"
1. Find library in question.
2. If concerned with particular methods/fields, use call-step/dataflow-step.
3. If concerned with entire library, put library into Connection View leaves pane. We'll choose this option to display a reverse call graph of the entire package. Enter the package into the Connection View either by dragging and dropping it into the leaves pane or by right-clicking the package and selecting Atlas -> Connection View -> Add To Leaves.
The resulting graph shows us a graph of all calls that lead to the android.content.pm package. We can see that the package we're concerned with is used by three methods in two classes.
4. Either put relevant classes and methods into roots pane, or put items into omissions pane. We will do the former.
5. Calls now visible more explicitly
6. Double-click on other calls to examine them in the source code. Let's look at the other method in our class that calls android.content.pm first. Double-clicking the method takes us to the method declaration, or double-clicking the edge directly highlights the line where the library is called.
7. Next, we can see that the only other class accessing the library in question has multiple reads from one method.
