.TH listthreads 1P local "Silicon Graphics, Inc."
.SH NAME
listthreads \- List the threads running in target system
.SH SYNOPSIS
\f3listthreads\f1 process
.SH DESCRIPTION
The 
.B listthreads
command sends a message asking for the IDs of any threads running on the target system via
.I dbgif
and displays the result of the command on stdout. The
.B process
argument is not used in the Ultra 64 system, but is required by this command
(which is also part of other debuggers). It must be a number, but any number
will do, since the value is ignored by the target. The number 42 is quite popular.
.PP
Since this command is very independent of the application running in the target,
it is the canonical command for testing communications between target and host. If you suspect there is a communications problem, it is often useful to run
.I listthreads
to see if the target is answering before attempting to start the debugger.
A message will be displayed if it is not possible to retrieve target information.
.PP
Before execution of this command, the
.I dbgif
program must be running and the
.I METHOD
environment variable must be set to indicate if 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
.SH SEE ALSO
dbgif(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.