> 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.
drop down debugger list
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
starting new process
## 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+ ```
attaching to process
IDA will then attach to the selected process, and leave it suspended at the place it was when it was attached to:
attached to process
--- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.hex-rays.com/8.5/user-guide/debugger/debugger-tutorials/debugger_linux_local.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.