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.
Processor
This option is only visible when starting debugger without a database. 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
Last updated
Was this helpful?