> 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/ida-9.3/core/debugger/concepts/remote-debugging/remote-gdb-debugger/remote-gdb-debugger-options.md).

# Remote GDB Debugger options

## Max packet size

Maximum packet size supported by the GDB stub (in bytes). Some stubs can crash on big packets, e.g. memory reads. IDA will try to split such requests in smaller chunks so that replies should fit in this size. You can enter `-1` to autodetect (in this case IDA will use the size of the "g" packet reply as the max packet size).

## Timeout

Default timeout in milliseconds for remote GDB stub responses. Some targets can be slow to respond, so increase this value when having problems, e.g., with disappearing memory bytes.

## Run a program before starting debugging

Check to enable [external program options](/ida-9.3/core/debugger/concepts/remote-debugging/remote-gdb-debugger/external-programs-and-gdb-debugger.md).

## Processor

This option is only visible when [starting debugger without a database](/ida-9.3/core/debugger/concepts/instant-debugger.md). Use it to specify on which CPU the target is running. For some processors you can also specify the endianness.

## Software breakpoints at EIP+1

Most GDB stubs for x86 report software breakpoint hits with EIP one byte after the breakpoint address. However, some emulators report the actual breakpoint address. This option allows IDA to recognize such situations.

{% hint style="info" %}

#### Recommendations

Uncheck for QEMU, check for others.
{% endhint %}

## Use CS:IP in real mode

When debugging real-mode (16-bit) code, the stub can send either just 16 bits of IP register or the full EIP (CS<<4 + IP). Enable this option in the former case.

{% hint style="info" %}

#### Recommendations

Check for QEMU, uncheck for others.
{% endhint %}

See also

* [Instant debugger](/ida-9.3/core/debugger/concepts/instant-debugger.md)
* [Remote GDB Debugger](/ida-9.3/core/debugger/concepts/remote-debugging/remote-gdb-debugger.md)


---

# 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/ida-9.3/core/debugger/concepts/remote-debugging/remote-gdb-debugger/remote-gdb-debugger-options.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.