JP2000099364A - Method for debugging device driver - Google Patents

Abstract

PROBLEM TO BE SOLVED: To enable debugging without preparing any dedicated debugging object device driver and changing any internal code by monitoring a request packet to be dispatched from an operating system(OS) to the debugging object device driver and controlling the output of input/output data. SOLUTION: When a computer is activated, an OS 4 and a debugging object device driver 6 are integrated onto an internal RAM 2. Next, a device driver 5 for debugging is integrated onto the RAM 2 and during that integrating processing, processing is performed for hooking the entry routine of the debugging object device driver 6. Then, this method uses a device driver 5 for debugging provided with a method for controlling the output of output data by monitoring the request packet to be dispatched from the OS 4 to the debugging object device driver 6.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

The present invention relates to an output process for debugging in a device driver, such as when a device driver is created for a final form in which software is actually used (hereinafter referred to as a release version). The present invention relates to a device driver debugging method for easily controlling output of request packet data for debugging without changing a device driver even if the device driver does not have the device driver.

[0002]

2. Description of the Related Art A conventional debugging method of a device driver uses a dedicated debugging tool, and a debugging output is included in a source code of the device driver so that the dedicated debugging tool can handle symbol information of the device driver. In this method, a debugging-specific device driver that differs from the release version is created by embedding the code, adding debugging options to it, and assembling and compiling.

[0003]

However, in the above-described conventional device driver debugging method, there is a problem that a device driver dedicated to debugging different from the original release version device driver has to be created, and the release version device driver itself has to be created. There is a problem that a complicated method is required when debugging. Also,
In order to perform such debugging, there is a problem that a system for operating the device driver to be debugged and a system for controlling the device driver for debugging are required.

SUMMARY OF THE INVENTION The present invention solves the above-mentioned problem. By using a device driver for debugging, a device driver to be debugged is not created exclusively for debugging, and without changing an internal code. It is an object of the present invention to provide a device driver debugging method capable of performing debugging with only one system in which a debug target device driver operates.

[0005]

SUMMARY OF THE INVENTION In order to solve the above-described problems, the present invention provides a debugger having a method of monitoring a request packet passed from an operating system to a device driver to be debugged and controlling the output data of the request packet. By using the device driver for debugging, the device driver to be debugged can be easily debugged without creating a device driver for debugging exclusively for debugging and without changing the internal code. Debugging is performed by only one system running.

[0006]

DESCRIPTION OF THE PREFERRED EMBODIMENTS The present invention according to claim 1 of the present invention provides means for acquiring a device driver name to be debugged from a parameter line of a device driver for debugging, means for storing the acquired device driver name, and storage. Means for finding a matching device driver name from the device list of device drivers registered by the system using the device driver name stored in the means and obtaining an entry point for processing a request packet from the operating system; Means for storing an entry point, and incorporating a device driver for debugging with the same name as the device driver for debugging by using the device driver name stored in the storage means in the system, thereby providing the device driver for debugging and the device driver for debugging. Means for replacing the request packet, means for storing a request packet passed from the operating system to the debugging device driver, and request packet stored in the storage means for debugging the request packet using the entry point stored in the storage means. Means for passing to the entry point of the device driver, means for storing a request packet returned from the device driver to be debugged, and checking whether the request packet passed to the device driver for debugging is a request packet for a debug data output request,
Means for outputting, to a standard output, the data content of the request packet stored in the storage means when the request packet is a debug data output request, and monitors the request packet passed from the operating system to the device driver to be debugged. This is a method of debugging a device driver that controls output of its input / output data without creating a debug target device driver exclusively for debugging, without changing internal code, and operating the debug target device driver.
It has the effect of debugging with only one system.

Hereinafter, embodiments of the present invention will be described with reference to the drawings. (Embodiment) FIG. 1 is a configuration diagram of an embodiment of a system for implementing a device driver debugging method according to the present invention, wherein 1 is a processor, 2 is a random access memory (RAM) inside a computer, and 3 is on a RAM 2. Application 4, an operating system on the RAM 2, a debugging device driver 5 on the RAM 2, an area 51 for storing a device driver name in the debugging device driver 5, and an entry point 52 in the debugging device driver 5. An area for storing 53 is an area for storing a request packet passed from the operating system 4 in the debugging device driver 5, and an area 54 is returned from a debugging target device driver 6 described later in the debugging device driver 5. Area for storing the request packet, 6 debugged device drivers on the RAM 2, 7 is the debug target device device driver 6 controls, 8 is a standard output device.

FIG. 2 is a flowchart showing the operation of the system having the above configuration. When the computer is started, in step 1, the operating system 4 and the debug target device driver 6 are installed on the RAM 2 inside the computer. In step 2, the debugging device driver 5 is stored in the RAM 2 inside the computer.
For hooking an entry routine of the device driver 6 to be debugged during the embedding processing (when the processing of the target software is called, the called place is intercepted and processed first). Is performed. In step 3, the debugging device driver 5 obtains the name of the debugging target device driver 6 from the parameter line, and saves the obtained debugging target device driver 6 in the area 51 of the debugging device driver 5 that stores the device driver name. . In step 4, the debugging device driver 5 acquires the device driver names of the six device drivers to be debugged from the area 51 storing the device driver names. In step 5, the debugging device driver 5 finds a matching device driver name from the device list of device drivers registered by the system, obtains an entry point, and saves the entry point in the area 52 of the debugging device driver 5 that stores the entry point. I do. In step 6, the debugging device driver 5 acquires the device driver name from the area 51 storing the device driver name, and
The device name of the debug target device driver 6 is set to the same name as the device name of the debug target device driver 6, and the process for incorporating the device name of the debug target device driver 6 into the system ends. According to such a procedure, the debug target device driver 6 and the debug device driver 5 can be replaced, and the entry point of the debug target device driver 6 can be hooked. A request packet from the operating system 4 to be transmitted is indirectly passed through the debugging device driver 5.

At step 7, a request packet passed from the operating system 4 to the debugging device driver 5 is issued. In step 8,
The request packet passed to the debugging device driver 5 is checked to determine whether it is a request packet for a debug data output request. If it is a request packet for a debug data output request, go to step 9 and perform the process of step 9. If it is not a request packet for a debug data output request, go to step 10 and go to the process of step 10. In step 9, the debugging device driver 5
Request packet data from an area 53 in the debug device driver 5 that stores a request packet from the debugger, and request packet data from an area 54 in the debug device driver 5 that stores a request packet from the debug target device driver 6. get. In step 11, the debugging device driver 5 converts the data acquired in step 9 from binary data to ASCII data, and outputs this data to the standard output device 8. In step 10, the debugging device driver 5 saves the request packet passed from the operating system 4 to the debugging device driver 5 in an area 53 of the debugging device driver 5 that stores the request packet. In step 12, the debugging device driver 5 acquires the entry point from the area 52 in the debugging device driver 5 that stores the entry point, and acquires the request packet from the area 53 that stores the request packet. The request packet is passed to the indicated device driver 6 to be debugged. In step 13, the debug device driver 5 receives the request packet returned from the debug target device driver 6 in which the execution result of the passed request packet is set, and stores the request packet in the area 54 for storing the request packet.
To save. In step 14, the debugging device driver 5 acquires the request packet from the area 54 in the debugging device driver 5 that stores the request packet from the debugging target device driver 6. In step 15, the debugging device driver 5 returns a request packet to the operating system 4. Thereafter, the procedure from step 7 is repeated.

According to the above-described method, the execution result of the device driver required for debugging can be obtained from the standard output without changing the device driver 6 to be debugged.

[0011]

As described above, according to the device driver debugging method of the present invention, the device to be debugged can be easily created without creating the device to be debugged exclusively for debugging and without changing the internal code. The request packet passed from the operating system for debugging the driver to the device driver to be debugged can be monitored, and the result can be obtained from the standard output. Further, debug information can be obtained only by one system in which the debug target device driver operates.

[Brief description of the drawings]

FIG. 1 is a configuration diagram of an embodiment of a system that implements a device driver debugging method of the present invention.

FIG. 2 is a flowchart showing the operation of the system of FIG. 1;

[Explanation of symbols]

 Reference Signs List 1 processor 2 random access memory (RAM) 3 application 4 operating system 5 device driver for debugging 6 device driver for debugging 7 device 8 standard output device 51 area for storing device driver name 52 area for storing entry point 53, 54 request packet Area to store

Claims (1)

[Claims] In a debugging method by a device driver for finding and correcting an inconvenience of a program (hereinafter, referred to as debugging), means for acquiring a name of a device driver to be debugged from a parameter line of a device driver for debugging, Means for storing the registered device driver name, and using the device driver name stored in the storage means, to find a matching device driver name from a device list of device drivers registered by the system, and to process a request packet from the operating system. Means for acquiring an interrupt pointer (hereinafter, referred to as an entry point), a means for storing the acquired entry point, and a device having the same name as the device driver to be debugged using the device driver name stored in the storage means. Means for replacing the debug target device driver and the debug device driver by incorporating the debug device driver into the system; means for storing a request packet passed from the operating system to the debug device driver; and request stored in the storage means. Means for delivering the request packet to the entry point of the device driver to be debugged using the entry point stored in the storage means, means for storing the request packet returned from the device driver for debugging, and device device for debugging. It is checked whether the passed request packet is a request packet for a debug data output request, and if the request packet is a request packet for a debug data output request, the request packet stored in the storage means is checked. And means for outputting the data contents of Est packet to standard output, debug a device driver for outputting control the input and output data to monitor the request packet is passed to the debug target device driver from the operating system.