JP2002268928A - Method for checking version of executable file and library file - Google Patents

Abstract

PROBLEM TO BE SOLVED: To inform a user of detailed cause of malfunction of application created by using common library information and to shorten the time to analyse the cause. SOLUTION: An executable file 104 and library files 103a, 103b to manage the library information registered in the execution file have the library information respectively, both pieces of the library information are collated with each other in the case of execution of the application and the modified contents of the detected library information is displayed on a modification informing picture 105.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

[0001] 1. Field of the Invention [0002] The present invention relates to a method for checking the version of an executable file and a library file by using library information to check for a difference between the executable file and the library file.

[0002]

2. Description of the Related Art In a current application, all functions are not included in a generated executable file, but common library information (unique library information and library information provided by a vendor) is used. In general, a method for realizing each function is described below.

By the way, such common library information may be changed without the user's knowledge by applying a patch that changes a program by directly rewriting an executable file or installing another application. Many.

[0004]

Then, in the application created using the common library information, if the change is related to a part of the functions, all the functions can be realized without any problem until now. However, due to the change, the operation is suddenly terminated with an operation failure state of insufficient function realization, and there is a case where the terminal cannot be used.

At this time, since the user is not notified of the cause of the operation failure that has been terminated due to insufficient function realization, there is a problem that the user needs a considerable amount of time to specify the cause.

In view of the above circumstances, the present invention notifies the user of the detailed cause of the malfunction of an application created by using common library information, and shortens the time required to elucidate the cause of the version of the executable file and the version of the library file. It is intended to provide a checking method.

[0007]

In order to achieve the above object, a method for checking the version of an executable file and a library file according to claim 1 manages an executable file and library information registered in the executable file. The library file has library information. When the application is executed, the library files are compared with each other, and the detected contents of the library information are displayed.

According to the first aspect of the present invention, when the application is executed, the user is notified of the changed contents of the library information. Therefore, the user can know that the malfunction is due to the upgrade of the library information. Can be obtained, and a means for investigating the cause can be easily obtained.

According to a second aspect of the present invention, in the version checking method of the executable file and the library file according to the first aspect, when the executable file is generated, the executable file and the library file are extracted from the library file. If the library information has already been registered in the executable file, the two library information are compared, and if they are different, the changed content is displayed, and the library information registered in the executable file is updated to the latest one. It is characterized by the following.

According to the second aspect of the present invention, when the execution file is generated, the user is notified of the changed contents of the library information, so that the user can know in advance the version upgrade of the library information.

According to a third aspect of the present invention, there is provided a method for checking the version of an executable file and a library file according to claim 1 or 2, wherein the collation and display are performed by the execution file. Out of the list of attributes included in the library information obtained from the list of attributes included in the library information that is obtained from the library file and is present on the executable file,
It is characterized in that it is performed by collating the contents of the basic attribute items and setting the contents of the changed attribute on the library change notification screen.

According to the third aspect of the invention, the collation of the library information and the display of the result are performed at the level of the basic attribute item, so that the user can know in detail the item causing the malfunction due to the version upgrade. it can. Therefore, when an application becomes unusable, the user can understand which library information is causing the problem and what kind of problem is occurring, greatly reducing the time required to find out the cause of the malfunction. become able to.

[0013]

FIG. 1 is a diagram showing an embodiment of a method for checking the version of an executable file and a library file according to an embodiment of the present invention.

In FIG. 1, an executable file generation resource 10
1 has a source file 102. From this source file 102, two library files 103a, 1
03b is extracted as a library file containing library information used in the execution file 104 when the execution file 104 is generated.

In the illustrated example, the library file 103a
Contains library information of “functoin10”, “functoin11”, and so on. Library file 1
03b includes “functoin20”, “functoin21”,.
Library information is included.

When the execution file 104 is generated, library information to be used is stored in two library files 103.
a and 103b and registered in the execution file 104. In the illustrated example, the executable file 104
Includes “functo” included in the library file 103a.
in10 ”,“ functoin11 ”and library file 103
“functoin 21” included in “a” is registered.

When the application is started in accordance with a user's instruction, the library information registered in the execution file 104 and the library files (library files 103a and 103b in the illustrated example) obtained from the library information are managed. If the contents of the library information are different,
The changed library information is displayed on the library change notification screen 105 to notify the user of the changed information.

FIG. 2 shows an example of the data structure of library information used in the present embodiment. FIG. 2A shows the data structure of the management library information held in the library files 103a and 103b. FIG. 2 (2)
6 is a data structure of used library information held on an execution file 104.

As shown in FIG. 2, in the data structure of the library information, various information is stored in a tree structure for each library function, and the information is managed in an object-oriented manner. The basic attributes include items such as version, I / F specifications, usage, processing outline, and degree of influence. Items can be added as needed for each function.

FIG. 3 is a detailed explanatory diagram of a method for checking library information. FIG. 3A shows the library file 10
It is an example of management library information held on 3a and 103b. FIG. 3B shows an example of the used library information stored in the execution file 104.

As shown in FIG. 3, in the library information collation, for each library function registered in the library information of the executable file, each basic item (version, I / F specification, usage, processing outline, influence The collation of the contents is performed every degree).

FIG. 4 is an explanatory diagram of a library change notification screen for notifying a user that a library file has been changed, and a notification method. As shown in FIG. 4, the library change notification screen 105 includes a column of screen name “library change notification” and a column of contents. In the content column, first, a notice "The version of the library used in the executable file has been changed. If it is used as it is, the application may not operate properly." Subsequent and subsequent changes are displayed so that they can be specifically identified.

In the illustrated example, first, the target “executable file:
sample.exe "and" library function: funcTotal (file name: sample.dll) "are displayed. Next, the version “02.01.199911120” in the library function funcTotal of the used library information 401 on the execution file 104 is displayed as <conventional library>.

Next, as <changed content>, a changed portion in the corresponding library function funcTotal of the management library information 402 on the library files 103a and 103b is displayed. In the illustrated example, the version is changed to “02.08.2000110”, the usage is changed to “the value to be passed as a parameter is converted into a positive integer in advance”, and the degree of influence is changed in “: funcAA, funcBB. used."
Is displayed as changed.

As described above, the library change notification screen 10
5, the executable file 104 and the library file 10
As a result of comparing the library information of 3a and 103b,
The changed contents of the basic attribute items having different contents are set and can be notified to the user.

Next, the collation processing operation according to the present embodiment will be described with reference to FIGS. FIG. 5 is a flowchart illustrating an operation in which a collation process is performed when an execution file is generated. FIG. 6 is a flowchart illustrating an operation in which the matching process is performed when the application is executed. FIG. 7 is a flowchart showing the library information collation processing operation.

First, the collation processing at the time of generating an execution file is as follows.
This is performed as follows. In FIG. 5, when the execution file 104 is generated from the execution file generation source 101,
A list of library information used in the execution file 104 is obtained from the target library files 103a and 103b (step S501), and it is determined whether the library information of the obtained library function is not registered in the execution file 104 (step S502). ).

If the library information of the obtained library function has not been registered in the execution file 104 (step S502: Yes), a new library function is used. Register the library information (step S50
3), an execution file 104 is created using it (step S508).

On the other hand, if the library information of the obtained library function has already been registered in the execution file 104 (step S502: No), the execution file 104
Library information and library files 103a,
3b is checked by the method described later with reference to FIG. 7 (step S504), and it is checked whether they are different (step S505).

If the library information of the execution file 104 is not different from the library information of the library files 103a and 103b (step S505: No), the process proceeds to the execution file creation processing (step S508). If they are different (step S505: Yes), since the version of the library information has been changed, the user is notified that the library information has been changed (see FIG. 4).
(Step S506), and the library information of the execution file 104 is updated to the latest one (step S50).
7), the process proceeds to the execution file creation process (step S)
508).

As described above, when the library information registered in the execution file at the time of generating the application is different from the library information of the library file, the user is notified. You can know if it is up.

Next, the collation processing at the time of executing the application is performed as follows. In FIG. 6, when the application is activated, a list of library information registered in the execution file 104 is obtained (step S60).
1). Further, library information of the library function used in the execution file 104 is obtained from the library files 103a and 103b (step S602). Then, the contents of the library information of the execution file 104 and the library files 103a and 103b acquired as described above are collated by a method described later with reference to FIG. 7 (step S603), and it is checked whether they are different (step S6).
04).

Execution file 104 and library file 1
If the library information of the library file 03a and the library information of the library file 103b are the same (step S604: No), the library file 1
In versions 03a and 103b, since the version has not been upgraded, the application is activated as usual (step S605).

However, if the library information is different (step S604: Yes), the library file 1
In versions 03a and 103b, since the version has been upgraded, the user is notified that the library information has been changed (see FIG. 4) (step S606).
The user's intention is confirmed whether or not to continue the activation of the application (step S607). The user determines whether to continue with reference to the “impact degree” of the basic attribute item or the like.

As a result, when it is determined that the user starts the application (step S607: Yes)
s) to start the application (step S60)
8) If it is determined not to start (step S60)
7: No), the process ends without starting.

As described above, when the library information registered in the execution file differs from the library information of the library file when the application is executed, the user is notified in detail of the change, and the user is notified of the change. It is possible to determine whether to start the application according to the content and degree of the application.

Next, the collation processing of the library information is performed as follows. In FIG. 7, a list of attributes included in the library information of the library function existing on the operation execution file 104 is obtained (step S701).
Further, a list of attributes included in the library information of the library function existing in the execution file 104 is obtained from the library files 103a and 103b (step S).
702). Then, in the attribute list of the library information acquired as described above, the basic attribute item (version, I
/ F specification, usage method, processing outline, impact degree) are collated (step S703), and the contents are checked whether they are different (step S704).

As a result, if there is a change in the contents of the basic attribute item (step S704: Yes), the contents of the changed attribute are set on the library change notification screen 105 as illustrated in FIG. Step S705).

As described above, according to the present embodiment, when an application becomes malfunctioning and cannot be used due to a change in library information due to application of a patch, installation of another application, or the like, the user can use any library information. The problem can be identified and what kind of problem is occurring, and it is easy to take appropriate measures promptly.

At this time, since the influence is also notified to the user, the user can determine whether to start the application as it is, and can take appropriate measures individually according to the specific contents of the version upgrade. Become.

[0041]

As described above, according to the present invention,
When starting the application, the library information of the created executable file and library file is checked and the user is notified in detail of the cause of the malfunction. Can be shortened.

[Brief description of the drawings]

FIG. 1 is a diagram showing an embodiment of a method for checking a version of an executable file and a library file according to an embodiment of the present invention;

FIG. 2 is a diagram showing an example of a data structure of library information used in the present embodiment. (1) is a data structure of management library information held in a library file. (2) is a data structure of used library information held in the execution file.

FIG. 3 is a detailed explanatory diagram of a method for checking library information. (1) is an example of management library information stored in a library file. (2) is an example of the used library information stored in the execution file 104.

FIG. 4 is an explanatory diagram of a library change notification screen and a notification method for notifying a user that a library file has been changed.

FIG. 5 is a flowchart illustrating an operation in which a matching process is performed when an execution file is generated.

FIG. 6 is a flowchart illustrating an operation in which a matching process is performed when an application is executed.

FIG. 7 is a flowchart illustrating a collation processing operation of library information.

[Explanation of symbols]

101 execution file generation resource 102 source file 103a, 103b library file 104 execution file 105 library change notification screen 401 library information used in execution file 402 management library information managed in library file

Claims (3)

[Claims] 1. An executable file and a library file for managing library information registered in the executable file each have library information. When the application is executed, the library information is compared with each other, and the detected library information is changed. Displaying a version of the executable file and the library file. 2. The version checking method of an executable file and a library file according to claim 1, wherein at the time of generating the executable file, if library information extracted from the library file is already registered in the executable file, A method of checking the versions of an executable file and a library file, wherein the two library information are compared, and if they are different, the contents of the change are displayed and the library information registered in the executable file is updated to the latest one. 3. The version check method of an executable file and a library file according to claim 1 or 2, wherein the collation and display include a list of attributes included in library information acquired from the executable file and the library. The library information obtained from the file, of the list of attributes included in the library information present on the executable file, the contents of the basic attribute items are compared,
A method for checking the version of an executable file and a library file, wherein the method is performed by setting the content of the changed attribute on a library change notification screen.