writeword.1
1.39 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
.TH writeword 1P local "Silicon Graphics, Inc."
.SH NAME
writeword \- write data to a target system location
.SH SYNOPSIS
\f3writeword\f1 id vaddr data
.SH DESCRIPTION
The
.B writeword
command sends a request to write a word into the memory space of the
target system
via
.I dbgif.
The
.B id
is the thread number. Even though all threads share the same address
space, you must still specify a thread. This command is shared with
other debuggers in which threads may have different address spaces.
The virtual address
.B vaddr
is the location to write, and it must be on a word boundary. The
32-bit
.B data
is the value to be written.
.PP
Before execution of this command, the
.I dbgif
program must be running and the
.I METHOD
environment variable must be set to indicate whether this is a request for the
R4300 CPU or the coprocessor. The value zero represents the CPU and the number
one represents the RCP. In
.I csh,
this is accomplished by specifying
.IP
setenv METHOD 0
.PP
If METHOD is set to 1 and the coprocessor was running, the request will probably fail (as it should).
It is generally unwise to use METHOD 1 for this command anyway; all addresses
may be accessed from the CPU.
.SH SEE ALSO
dbgif(1P), listthreads(1P), readmem(1P)
.SH BUGS
In the event of a communications failure, the program will dump core. It
would be nice if it cleaned up after itself, but at present the core file
must be removed manually.