This page was produced by an automated import process, and may have formatting errors; feel free to fix.

Registers and Memory

GDB’s model of the target machine is rather simple. GDB assumes the machine includes a bank of registers and a block of memory. Each register may have a different size.

GDB does not have a magical way to match up with the compiler’s idea of which registers are which; however, it is critical that they do match up accurately. The only way to make this work is to get accurate information about the order that the compiler uses, and to reflect that in the gdbarch_register_name and related functions.

GDB can handle big-endian, little-endian, and bi-endian architectures.

None: Internals Registers-and-Memory (last edited 2013-08-20 23:41:20 by StanShebs)

All content (C) 2008 Free Software Foundation. For terms of use, redistribution, and modification, please see the WikiLicense page.