# Debug your application with RenderDoc for Arm GPUs

## In this learning path

- [Introduction](https://learn.arm.com/learning-paths/mobile-graphics-and-gaming/ams/)
- [Set up Arm Performance Studio](https://learn.arm.com/learning-paths/mobile-graphics-and-gaming/ams/ams/)
- [Set up an Android application for profiling](https://learn.arm.com/learning-paths/mobile-graphics-and-gaming/ams/setup_tasks/)
- [Interpret an example Arm Streamline report](https://learn.arm.com/learning-paths/mobile-graphics-and-gaming/ams/streamline_example/)
- [Use Arm Streamline to capture data for your application](https://learn.arm.com/learning-paths/mobile-graphics-and-gaming/ams/streamline/)
- [View an example Performance Advisor report](https://learn.arm.com/learning-paths/mobile-graphics-and-gaming/ams/pa_example/)
- [Create a Performance Advisor report for your application](https://learn.arm.com/learning-paths/mobile-graphics-and-gaming/ams/pa/)
- [Analyze your application with Frame Advisor](https://learn.arm.com/learning-paths/mobile-graphics-and-gaming/ams/fa/)
- [Debug your application with RenderDoc for Arm GPUs](https://learn.arm.com/learning-paths/mobile-graphics-and-gaming/ams/renderdoc/)
- [Analyze shader program performance with Mali Offline Compiler](https://learn.arm.com/learning-paths/mobile-graphics-and-gaming/ams/malioc/)
- [Next Steps](https://learn.arm.com/learning-paths/mobile-graphics-and-gaming/ams/_next-steps/)

## Run RenderDoc for Arm GPUs
[RenderDoc for Arm GPUs](https://developer.arm.com/Tools%20and%20Software/RenderDoc%20for%20Arm%20GPUs) is an Arm fork of the [RenderDoc](https://renderdoc.org/) open-source debugger.

The Arm release includes support for API features and extensions that are available on the latest Arm GPUs, but not yet supported in upstream RenderDoc. Arm intends to contribute changes to the upstream project, but some Arm-specific or Android-specific features might be available only in the Arm fork.

To run RenderDoc for Arm GPUs:

1. Open RenderDoc for Arm GPUs and select your connected device from the **Replay Context** dropdown list at the bottom left of the RenderDoc UI.
   
   ![Screenshot of the RenderDoc Replay Context selector at the bottom left, where you choose the connected Android target before launching the app](https://learn.arm.com/learning-paths/mobile-graphics-and-gaming/ams/images/rd_replay_context.png)

   The RenderDoc APK starts running on your target. If you don’t see your device, check that your device is set up correctly as described in [Setup tasks](https://learn.arm.com/learning-paths/mobile-graphics-and-gaming/ams/setup_tasks/).

2. Navigate to the **Launch Application** tab, and set the **Executable Path** to the application that you want to debug. Select the **Browse** button to view all of the installed application packages on the target and find the `.exe` file.

3. Select **Launch**, to start the application running on your target. After a successful launch, a new target-specific tab opens in the UI where you can select the frames that you want to capture.

   ![Screenshot of RenderDoc for Arm GPUs showing an established Android target connection, capture frame controls, and collected frame thumbnails](https://learn.arm.com/learning-paths/mobile-graphics-and-gaming/ams/images/rd_capture_controls.png)

   As your application runs, you can choose to:
   - Capture one or more frames immediately
   - Capture one or more frames after a delay
   - Capture one or more frames after a specific frame

   Use these controls to take captures of your application as it runs on the target device. Captured frames are stored temporarily on the device.

4. When you’ve finished capturing the frames of interest, stop the application that you are debugging. Keep RenderDoc running so that you can analyze and debug your captures.

5. Select a capture from the **Captures collected** window and select **Open**. When the frame has loaded, it’s displayed on the target and in the **Texture Viewer** tab, and the **Event Browser** is populated.

   ![Screenshot of a captured frame opened in RenderDoc showing the Event Browser, Texture Viewer, API Inspector, and output preview for the selected event](https://learn.arm.com/learning-paths/mobile-graphics-and-gaming/ams/images/rd_full_ui.png)

   By default, the **Event Browser** shows all `action()` events, which include draws, copies, and clears. Enter a search term in the **Filter** dropdown to filter these events.

   ![Screenshot of the RenderDoc Event Browser filtered for draw events with a selected draw call highlighted for debugging frame state](https://learn.arm.com/learning-paths/mobile-graphics-and-gaming/ams/images/rd_event_browser.png)

   Selected events are highlighted with a green flag. The other windows in the UI update to display information for the selected event, including the render state, data resources, and GPU output.

For a full list of features, see the [RenderDoc documentation](https://renderdoc.org/docs/index.html#).

## What you’ve accomplished and what’s next
You’ve now run RenderDoc for Arm GPUs on your application and learned how to capture frames and select events for debugging.

Next, you’ll run Mali Offline Compiler to compile shaders and generate performance reports.