VIRTUTECH CONFIDENTIAL    Previous - Up - Next

gdb-remote

Provided by

gdb-remote

Class Hierarchy

conf-object → log-object → gdb-remote

Interfaces Implemented

log_object, event_poster

Description

The gdb-remote module allows a GDB session to connect to Simics and control the execution. An object of class gdb-remote is used to accept incoming GDB connection requests.

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:

Architecture	--target	GDB command
alpha	alpha-unknown-linux-gnu
armbe	armbe-unknown-linux-gnu
armle	armle-unknown-linux-gnu
ia64	ia64-unknown-linux-gnu
mips32be	mips-elf-linux
mips32le	mipsel-elf-linux
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
V8	sparc-unknown-linux-gnu
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.

Attributes

Attributes inherited from class conf-object

attributes, classname, component, iface, name, object_id, queue

Attributes inherited from class log-object

access_count, log_buffer, log_buffer_last, log_buffer_size, log_group_mask, log_groups, log_level, log_type_mask

Attribute List

architecture

Pseudo attribute; read/write access; type: unknown type.

Architecture of target.

connected

Pseudo attribute; read-only access; type: b.

Returns true if the gdb-remote object is connected to a gdb, false if not.

context_object

Optional attribute; read/write access; type: unknown type.

Context object that this GDB session is attached to.

disconnect

Pseudo attribute; write-only access; type: unknown type.

Disconnects the remote GDB

follow_context

Pseudo attribute; read/write access; type: unknown type.

Set to non-zero if context should be followed.

large_operations

Optional attribute; read/write access; type: unknown type.

Set to non-zero if memory operations received from GDB should be performed as single operations instead of bytewise

listen

Pseudo attribute; read/write access; type: unknown type.

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

Pseudo attribute; read/write access; type: unknown type.

Processor to connect the GDB stub to.

signal

Pseudo attribute; write-only access; type: unknown type.

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.

Command List

Commands defined by interface log_object

log, log-group, log-level, log-size, log-type

Commands

disconnect	disconnect from the remote gdb
follow-context	follow context
info	print information about the device
signal	tell remote gdb we got a signal
target	set target CPU for gdb connection

Command Descriptions

<gdb-remote>.disconnect

Synopsis

<gdb-remote>.disconnect

Description

Disconnect from the remote GDB. See the Simics User Guide for a longer description of gdb-remote.

<gdb-remote>.follow-context

Synopsis

<gdb-remote>.follow-context [context]

Description

Set the GDB session to follow context. If context is not specified, the GDB session will stop following any context.

<gdb-remote>.info

Synopsis

<gdb-remote>.info

Description

Print detailed information about the configuration of the device.

<gdb-remote>.signal

Synopsis

<gdb-remote>.signal signal

Description

Send a signal to the remote GDB. See the Simics User Guide for a longer description of gdb-remote.

<gdb-remote>.target

Synopsis

<gdb-remote>.target [cpu-name]

Description

Set the target CPU for this remote GDB connection. One GDB connection can only debug instructions on a single CPU at a time.

VIRTUTECH CONFIDENTIAL    Previous - Up - Next