diff --git a/docs/html/images/tools/db-attachprocess.png b/docs/html/images/tools/db-attachprocess.png new file mode 100644 index 0000000000000..ca5418e15b60e Binary files /dev/null and b/docs/html/images/tools/db-attachprocess.png differ diff --git a/docs/html/tools/debugging/debugging-studio.jd b/docs/html/tools/debugging/debugging-studio.jd index e1d80b98fe2a0..7e54634278fb2 100644 --- a/docs/html/tools/debugging/debugging-studio.jd +++ b/docs/html/tools/debugging/debugging-studio.jd @@ -31,6 +31,7 @@ page.title=Debugging with Android Studio
You don't always have to restart your app to debug it. To debug an app that you're already -running:
+You don't always have to restart your app to debug it. To debug an app that +you're already running:
Click Attach debugger to Android process
+
.
.By default, the debugger shows the device and app process for the current +project, as well as any connected hardware devices or virtual devices on your +computer. Select Show all processes to show all processes on +all devices; the display includes any services that your app created as well as +system processes, for example.
+From the Debugger menu, you can select Java, +Native, or Hybrid. The latter two options are +available only if your project contains some native C or C++ source code.
+The Debug window appears. In this case, notice the two tabs to the +right of the Debug window title: one tab is for debugging native code and the +other for Java code, as indicated by -java.
+
+Separate debugging sessions have separate tabs and different port numbers, +which are displayed in parentheses in the tab.