Lists the threads currently running in the target system
listthreads through dbgif, it sends a message asking for the IDs of any threads currently running on the target system, and then it displays the result of the stdout command on standard output device. The process argument is not used in the Nintendo 64 system, but it is required by this command, which is also part of other debuggers. It must be a number, but any number will do, because the value is ignored by the target. The number 42 is generally used.
Because this command is totally independent of the application running in the target, you can use this command to test communications between target and host. If you suspect there is a communications problem, it is often useful to run listthreads to see if the target is answering before you try to start the debugger. A message will be displayed if it is not possible to retrieve target information.
Before executing this command, you must ensure that the dbgif program is running and that the METHOD environment variable is set to indicate if this is a request for the R4300 CPU or the co-processor (RCP). The value zero represents the CPU and the number one represents the RCP. In csh, this is accomplished by specifying:
setenv METHOD 0
In the event of a communications failure, the program dumps core. If this happens, you must manually remove the core file.
1999/04/30 Changed Format