> For the complete documentation index, see [llms.txt](https://docs.hex-rays.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hex-rays.com/8.5/user-guide/debugger/debugger-tutorials/debugger_linux_local.md).

# IDA Linux Local Debugging

## Debugging Linux Applications with IDA Pro, locally

Last updated on July 29, 2020 — v0.1

You may already know that IDA lets you debug an application from an already existing IDB, by selecting the debugger using the drop-down debugger list.

<figure><img src="/files/gaQebsNfaj7ggXmLtzze" alt="drop down debugger list"><figcaption></figcaption></figure>

However, it is also possible to start IDA in a way that it will initially create an empty IDB, and then either:

* start a new process under its control
* attach to an existing process

## Launch IDA with a fresh new process

To do so, you will have to launch IDA from the command line, like so:

```bash
ida -rlinux /bin/ls
```

IDA will then launch the **/bin/ls** program, and break at its entrypoint

<figure><img src="/files/rx2WLeMcjrmulenwHueL" alt="starting new process"><figcaption></figcaption></figure>

## Attaching IDA to an existing process

For this example, we’ll launch, from a shell, a **/usr/bin/yes** process, and attach to.

Now, we’ll launch IDA so it offers a selection of processes to (and use quick filtering (**Ctrl+F**) to quickly find our process):

```bash
ida -rlinux+
```

<figure><img src="/files/oXrPLSc3NHOyH1jVNPxG" alt="attaching to process"><figcaption></figcaption></figure>

IDA will then attach to the selected process, and leave it suspended at the place it was when it was attached to:

<figure><img src="/files/DBihh5GdEaV4gt2ZyQRt" alt="attached to process"><figcaption></figcaption></figure>


---

# 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, and the optional `goal` query parameter:

```
GET https://docs.hex-rays.com/8.5/user-guide/debugger/debugger-tutorials/debugger_linux_local.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.