# 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](https://docs.hex-rays.com/8.5/user-guide/debugger/remote-debugging/remote-gdb-debugger/external-programs-and-gdb-debugger). Processor This option is only visible when [starting debugger without a database](https://docs.hex-rays.com/8.5/user-guide/debugger/instant-debugger). 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.
        Recommendations: uncheck for QEMU, check for others.
```

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.
        Recommendations: check for QEMU, uncheck for others.
```

See also

* [Instant debugger](https://docs.hex-rays.com/8.5/user-guide/debugger/instant-debugger)
* [Remote GDB Debugger](https://docs.hex-rays.com/8.5/user-guide/debugger/remote-debugging/remote-gdb-debugger)


---

# Agent Instructions: 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.hex-rays.com/8.5/user-guide/debugger/remote-debugging/remote-gdb-debugger/remote-gdb-debugger-options.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.