JPH0434625A - Debugging supporting device - Google Patents

Abstract

PURPOSE:To prevent the operation in itself of a normal BASIC interpreter from being influenced even in debugging by controlling an objective rapid library described high level language by a debugging means during a period from the transfer of control to the debugging means up to its return. CONSTITUTION:When control is transferred from a BASIC interpreter language program 2 to a rapid library (high level language program) 3 to be debugged, a start trigger is outputted from a trigger generating means 31. At the time of receiving the start trigger, a symbolic debugging means 4 having the same function as that of a general symbolic debugger controls the BASIC program 2 until the reception of an end trigger and executes the debugging operation of the program 3 like a debugger with a normal task level. Consequently, a program described by other high level language integrated in the BASIC program 2 can be symbolically debugged by a practical machine.

Description

DETAILED DESCRIPTION OF THE INVENTION <Industrial Application Field> The present invention enables a program written in another high-level language program (for example, a compiler type) incorporated into a basic (BASIC) interpreted language program to be executed on an actual machine. This article relates to a debug support device that enables symbolic debugging.

<Prior Art> A device has been proposed in which a program written in another high-level language is incorporated into a program written in the RAS I C interpreter language, and the program can be called as a subroutine.

In this case, it is generally difficult to debug parts of other high-level languages using the debug function of the BASIC interpreter in a debug environment.

The reason is that the BASIC interpreter has to interpret the grammar of other high-level languages, and BASIC
This is because it is not realistic to provide such a function to a C interpreter.

<Problem to be solved by the invention> The inability to debug a program on an actual device has many disadvantages in supporting the language.

The present invention has been made in view of these points, and is based on the BAS
An object of the present invention is to provide a debugging support device that enables a program written in another high-level language incorporated in an IC interpreter language program to be symbolically debugged on an actual machine.

Means for Solving the Problems> The present invention for solving the above-mentioned problems provides an apparatus that enables a high-level language program written in another language to be incorporated into a BAS I C interpreter language program. A debugging means capable of symbolically debugging another high-level language program incorporated in an IC interpreter language program independently of the BASIC interpreter is provided, and a start trigger generation means is provided at the beginning of the high-level language program. Also, an end trigger generating means is provided at the terminal end, and the debugging means receives a start trigger and an end trigger output from each trigger generating means of the high-level language program, and debugs the high-level language program during that time. It is configured.

Function> When control is transferred from the BASIC interpreter language program to the high-level language program to be debugged, a start trigger is output from the trigger generation means.

The debugging means has the same function as a general symbolic debugger, and when it receives this start trigger, it puts the BASIC program under control until it receives the end trigger, and debugs the target high-level language program. , just like a normal task-level debugger.

<Example> Embodiments of the present invention will be described in detail below with reference to the drawings.

FIG. 1 is a conceptual diagram showing an embodiment of the present invention.

In the figure, reference numeral 1 denotes a device equipped with a microprocessor configured to be able to incorporate a high-level language program written in another language into a RASIC interpreter language program.

2 is a program in the RAS I C interpreter language installed in this device, and 3 is a program written in another high-level language (for example, compiler t11) incorporated in this program 2.

31 is a start trigger generation means provided at the beginning of the high-level language program 3, and 32 is an end trigger generation means provided at the end. Each of these trigger generation means is
The trigger signals are output at the timing when control is transferred from the IC program to the high-level language program 3 and from the high-level language program to the RAS IC program, and are configured in terms of hardware.

4 is a symbolic debugging means, which is configured to be able to symbolically debug independently of the BASIC program 2, and is configured to debug the start trigger and end trigger output from each trigger generation means 31 and 32 of the high-level language program 3. In response to this, the link position of the target program is known, and the high-level language program 3 is debugged during that time.

Figure 2 shows, for example, factory automation (F
A) is a conceptual configuration diagram showing an example of a case where a computer used in the field is equipped with the debugging means shown in FIG. 1.

This device is provided with at least two types of screens Sl and S2, and these screens can be switched by operating a keyboard or a mouse.

The RAS I C program 2 installed therein operates using the screen s1, and the symbolic debugging means 4 operates using the screen S2. 5 indicates a task area for executing a BAS I C program configured in memory, and the high-level language program 3 is a BAS I C program.
It is linked to the IC program in the form of a high-speed library. Here, a high-speed library written in a high-level language and a program that functions as the simplified device software means 4 are downloaded from the image file 6.

FIG. 3 is an operational conceptual diagram showing a symbolic debugging operation start procedure.

First, load the BASIC program in advance using screen S1 (LOADXXXXJ)
At the same time, link the high-speed library 3 written in the high-level language to be debugged (LINKLI
B YYYY) (■).

The debugging means 4 uses the screen S2 to determine the timing at which the start trigger is received (the high-speed library 3 to be debugged).
BASIC program 2 at the specified timing)
Notify the start of debugging of the high-speed library to (
Event notification) (■.

■). At the same time, it sets itself as an exception monitor task and puts the BASIC task under its control.

In this state, source files are referenced and breakpoints are set (■), and the BASIC task is
N” is done (■).

FIG. 4 is a conceptual diagram showing a procedure for transitioning a BASIC program to a debug state.

In response to "RUN" from the debugging means 4, the BASIC program returns to waiting for a command input, receives the aforementioned debug start event in response to a command input by the operator, and checks the link location of the designated high-speed library 3. Here, if the designated high-speed library is not found, an error event indicating that "the high-speed library does not exist" is notified to the debugging means 4, and the debugging state is not entered.

When the debugging means 4 receives this error event, it displays an error message on the screen and terminates.

When the designated high-speed library is found, a 5TART exception code and an END exception code are set at the beginning and end of the designated high-speed library, and the program enters the debug state. Then, the user programs are sequentially executed by the "RUN" command.

FIG. 5 is a conceptual diagram showing the debugging procedure of the high-speed library.

At the beginning of the high-speed library 3 to be debugged, a "start trigger j" (START
exception) occurs, and the debugging means 4 is notified of this. The debugging means 4 receives this start trigger and obtains the actual link address of the target high-speed library. First, the image is checked for identity with the image on the image file 6 (disc) based on the creation date and time, and if there is a mismatch, an error message is displayed and the system waits for command input.

If they match, debugging of the target high-speed library begins. Set the breakpoints specified above and complete the BA with the exception monitor task qualification.
Performs operation management of SIC tasks. In this state, the debugging means 4 enters the command manual state and debugs the high-speed library using various debugging commands.

Here, at the set breakpoint, “IL
A "LEGAL 1N5TRUCTION exception" occurs and is notified to the debugging means 4.

When the end of the target high-speed library is reached, an end trigger J (END exception) is generated by the trigger generation means 32, and this is notified to the debugging means 4.The debugging means 4 receives this end trigger and performs the setting. Restore the instruction code of the breakpoint,
Terminates debugging of the target high-speed library.

FIG. 6 is a conceptual diagram showing the processing procedure of BASIC commands.

For example, if the "5AVE" command is executed in debug state, 5TAR of the high-speed library to be debugged
Return the T/5TOP exception code to the original instruction code, and after saving, set the 5TART/5TOP exception code again.

Also, even if the program location is changed, 5T
The address is checked every time there is an ART/5TOP exception. In this case, breakpoints and the like are managed using relative addresses, so no problem occurs. Furthermore, when the program itself changes, such as LOAD/CHAIN/5TART, the program change notification is sent to the debugging means 4 and the debugging state is released.

When the debugging means 4 receives such a notification, it displays an error message and terminates.

The debugging means 4 returns the set breakpoint to the original instruction code by the debugging end command,
Sends a debug end notification to the BASIC program.

Upon receiving this notification, the BASIC program cancels the debug state, returns the 5TART/5TOP execution code of the target high-speed library to its original instruction, and returns to normal operation.

With the above operation, it is possible to symbolically debug a high-speed library written in a high-level language on the actual device using the debugging means only from the time control is transferred to the high-speed library to be debugged until the time the control is returned. can.

<Effects of the Invention> As described above in detail, according to the present invention, a debug support device having the following features can be provided.

(a) The target high-speed library written in a high-level language is
Since it is under the control of the debugging means from the time control is transferred to it until it returns, the normal operation of the BASIC interpreter itself is not affected even during debugging.

(b) By generating the start and end trigger signals of the debug operation using hardware,
The operation of the SIC program becomes the same as the actual operation, and reliability in debugging the actual device can be improved.

(C) Link position of high-speed library to be debugged (
address) changes dynamically due to modification of the BASIC program. A feature of the BASIC interpreted language is that the program can be dynamically modified while it is being debugged. The start trigger of debug operation causes
Since the link position of the target high-speed library can be recognized, debugging can be performed without losing the features of the BASIC interpreted language described above.

[Brief explanation of drawings]

FIG. 1 is a conceptual configuration diagram showing one embodiment of the present invention; FIG. 2 is a conceptual diagram showing an example of a configuration in which a computer used in the FA field is equipped with the debugging means shown in FIG. 1; Figure 3 is a conceptual diagram showing the steps to start symbolic debugging, Figure 4 is a conceptual diagram showing the steps to transition a BASIC program to the debug state, Figure 5 is a conceptual diagram showing the steps to debug a high-speed library, Figure 6 FIG. 2 is a conceptual diagram showing the processing procedure of BASIC commands. 1... Device equipped with a microprocessor 2... BAS
I C interpreter language program 3...High-level language program (high-speed library) 31...Start trigger generation means 32...End trigger generation means 4...Symbolic debugging means 6...Image file

Claims (1)

[Scope of Claims] In a device that enables a high-level language program written in another language to be incorporated into a BASIC interpreted language program, debugging means that can be symbolically debugged independently of the BASIC interpreter is provided in the high-level language program, a start trigger generation means is provided at the beginning of the high-level language program, and an end trigger generation means is provided at the end thereof, the debugging means includes: A debug support device characterized in that it receives a start trigger and an end trigger output from each trigger generation means of the high-level language program, and debugs the high-level language program during that time.