> For the complete documentation index, see [llms.txt](https://docs.devolutions.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.devolutions.net/rdm/knowledge-base/troubleshooting-articles/debugging.md).

# Debugging

{% tabs %}
{% tab title="Windows" %}
When an issue occurs, while using Remote Desktop Manager, our customer support technicians may ask you to turn on debugging and send the information back.

{% hint style="info" %}
Any debug level other than zero will slow down the application and write a lot of information in the application logs. As soon as you have completed the diagnostics, you should revert back the debug level to zero.
{% endhint %}

The Ad hoc debugging method is sufficient in most cases, use the in-depth debugging method whenever you need to diagnose the startup or the initial connection.

### Solutions

#### Ad hoc debugging method

1. In Remote Desktop Manager, open ***Help – Profiler***, move the window aside to clear the main window.
2. In the ***Debug only*** tab, click on the ellipsis button and activate the proper debug categories.
3. In Remote Desktop Manager, perform the action that is under investigation.

For timing session load times, please press <kbd>Ctrl</kbd>+<kbd>F5</kbd> to invalidate the cache and perform a full refresh. You should see debug information appear in the profiler window.

4. Click on ***Send trace to Support***.
5. In the following dialog, ensure you specify enough information to link the report to the appropriate ticket.

If the process was started from the forum include your forum username.

#### In-depth debugging method

1. In Remote Desktop Manager open ***File*** – ***Settings*** – ***Advanced***.
2. Click on the ***Debug level*** ellipsis button and activate the proper debug categories.
3. In the ***Information*** section, you will see a hyperlink to your configuration folder, press on it to have a file explorer window opened in that folder.
4. Close Remote Desktop Manager

As a preparatory phase, it would be best to clear existing logs to limit the scope of what will need to be analyzed.

5. Delete or rename files named RemoteDesktopManager.log, RemoteDesktopManager.log.db and RemoteDesktopManager.debug from your configuration folder.
6. Start Remote Desktop Manager.
7. Perform the action that is under investigation.
8. Open ***File – Settings – Advanced***, set the ***Debug level*** to zero.
9. Close Remote Desktop Manager.
10. Package the \*.log, \*.log.db and \*.debug files from your configuration folder and send them to us.
    {% endtab %}

{% tab title="macOS" %}
When an issue occurs, while using Remote Desktop Manager, our customer support technicians may ask you to turn on debugging and send the information back.

{% hint style="info" %}
Any debug level other than zero will slow down the application and write a lot of information in the application logs. As soon as you have completed the diagnostics, you should revert back the debug level to zero.
{% endhint %}

Use the debugging method whenever you need to diagnose the start-up or initial connection.

* Start by clicking on ***Help – Performance profiling***. Move the window aside to clear the main window of Remote Desktop Manager macOS.
* In the Debug only tab, click on the ellipsis button and activate the proper debug categories.
* In Remote Desktop Manager macOS, click on Flags to check what perform the action that is under investigation.
* Then, click on ***Send trace*** to support. In the following dialog, ensure you specify enough information to link the report to the appropriate ticket, if the process was started from the forum include your forum user name.
  {% endtab %}
  {% endtabs %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.devolutions.net/rdm/knowledge-base/troubleshooting-articles/debugging.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.