The following table lists, for each target architectures supported by gdb-remote, the string to give to configure as the --target parameter when building GDB, and any command you may have to enter at the GDB command prompt before connecting to Simics:
|mips64be||mips64-elf64-linux64||set mips abi n64|
|mips64le||mips64el-elf64-linux64||set mips abi n64|
|ppc32||powerpc64-elf-linux||set architecture powerpc:common|
|ppc64||powerpc64-elf-linux||set architecture powerpc:common64|
|sparc-v9||sparc64-sun-solaris2.8||set architecture sparc:v9|
|x86-64||x86_64-pc-linux-gnu||set architecture i386:x86-64|
|x86||x86_64-pc-linux-gnu||set architecture i386|
Note that these --target flags are not the only ones that will work, just examples of ones that do work.
Architecture of target.
Returns true if the gdb-remote object is connected to a gdb, false if not.
Context object that this GDB session is attached to.
Disconnects the remote GDB
Set to non-zero if context should be followed.
Set to non-zero if memory operations received from GDB should be performed as single operations instead of bytewise
Set to start listening for incoming GDB connections on the specified port. If 0 is specified an arbitrary available port will be used. Read to get the port currently listened on, or 0 if none.
Processor to connect the GDB stub to.
Sends a signal to the remote GDB. This makes GDB think the program it is debugging has received a signal. See the signal(7) man page for a list of signal numbers.
|disconnect||disconnect from the remote gdb|
|info||print information about the device|
|signal||tell remote gdb we got a signal|
|target||set target CPU for gdb connection|