Patent ID: 6016558
Filing Date: 2000-01-18
Classification: G06F

Abstract:
A communication event/message tracing method for an RPC-based distribution processing program includes the steps of:a first step in which a program and event list to be traced on an event tracing window of a debugging client is registered by a user and a debugging client reports the start of the event tracing to the debugging server in which a corresponding program exists;a second step in which the debugging servers reports a break point setting instruction to an event-related RPC library function to the rear debugger in accordance with the report in the first step;a third step in which the rear debugger sets a break point with respect to the RPC library function of the program in accordance with the instruction of the second step and the result is reported to the debugging server;a fourth step in which the debugging server reports to the debugging client that the event tracing operation is ready in accordance with the report of the third step;a fifth step in which the debugging client reports to the rear debugger through the debugging server so that the debugging client performs all programs related to the event tracing program in accordance with the report of the fourth step, and the rear debugger performs the program;a sixth step in which the ready debugger judges whether the rear debugger reaches the position where the break point is set during the operation of the program of the fifth step;a seventh step in which the fifth step is repeatedly performed when the break point does not reach the set position as a result of the judgement of the sixth step and the program is stopped at a corresponding position when the same reaches the set position, and the result thereof is reported to the debugging client through the debugging server;an eighth step in which the debugging client compares the break point with the event list in accordance with the report of the seventh step and judges whether the event is generated; anda ninth step in which the fifth step is repeatedly performed when the event is not generated as a result of the judgement of the eighth step and a receiving message and sending message of the sender and receiver are mapped when the event is generated, and the generation of the event is displayed on the event tracing window.