Remote Debugging of MIPS-Based Computers

 Last reviewed: September 23, 1996
Article ID: Q118887
The information in this article applies to:
  • Microsoft Windows NT operating system version 3.1
  • Microsoft Windows NT Advanced Server version 3.1

SUMMARY

This article details how to enable the debugger on a MIPS-based computer and how to use MIPSKD to remotely debug from an x86, MIPS, or Alpha platform.

MORE INFORMATION

Remotely debugging a MIPS-based computer requires a few steps that are different from debugging an x86-based computer. To set up for remote debugging on a MIPS-based computer:

  1. The MIPS debugger requires the base address of the kernel on the remote computer before any symbols load. To acquire the base address of the remote computer, MIPSKD must be connected to the remote computer through a reboot cycle. The kernel base address is then stored in a file called KERNBASE.DAT for future debug sessions on the same MIPS-based computer.

  2. The remote MIPS-based computer should have the debugger enabled to connect and create the KERNBASE.DAT file. To enable the debugger on a MIPS-based computer:

    a. From the Boot menu, choose Run Setup. b. Select Manage Startup. c. Select Change A Boot Selection. d. Select Windows NT 3.1 or Windows NT Advanced Server 3.1. e. Use the arrow keys to select OSLOADOPTIONS, and then press ENTER. f. Set the value to "/debug" (without the quotes), and then press ENTER.

  3. Set the modem to Auto Answer mode and disable DTR by typing "AT&D0S0=1" (without the quotation marks) in Terminal from another workstation, and then plug the modem in to the first available COM port on the MIPS-based computer.

  4. From the Boot menu of the remote MIPS-based computer, choose Windows NT 3.1 or Windows NT Advanced Server 3.1.

  5. Disable DTR on the local modem by typing "AT&D0" (without quotation marks) in Terminal.

  6. Connect to the remote MIPS-based computer. Select to shutdown and restart the MIPS-based computer after you are connected. When the MIPS- based computer is rebooted, select Windows NT 3.1 or Windows NT Advanced Server 3.1 from the Boot menu of the remote MIPS-based computer.

While Windows NT is loading on the remote MIPS-based computer, the debugger should automatically re-establish the session and create a KERNBASE.DAT file on your local hard disk.

You should now be able to dial into the MIPS-based computer, load symbols, and debug.

Additional reference words: prodnt 3.10
KBCategory: kbnetwork
KBSubCategory: ntras debugdoc

THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: September 23, 1996
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.