Patent US5319645A successfully refreshed from Google Patents.
← Back to Patent Explorer
US5319645A Expired / Lapsed US ⏱️ 0.0 years remaining

Method for debugging and testing the correctness of programs

Assignee: Bull SAS
•
Filing: 1991-07-30
•
Granted: 1994-06-07
•
Expires: 2011-07-30
📄 Original PDF 🌐 Google Patents 🔄 Sync Now

Abstract

Abstract Method for debugging and testing the correctness of programs, comprising the loading in a data processing system of a monitoring program, of at least a source program to be testing and of at least an object program achieved by the source program through a preprocessing which includes, at each executable program row, a call to a control routine, in the independent activation of a monitoring process based on the monitoring program and of a process to be tested, based on the object program, the two processes interacting by use of message queues.

Inventors

  • 👤 Flavio Bassi
  • 👤 Lucio Furlani
  • 👤 John Mason

Bibliographic Details

Application Number —
Jurisdiction US
Data Source google_patents
Last Synchronized 2026-10-25 04:21
CPC Classifications
G; G06; G06F; G06F11/00; G06F11/36; G06F11/3698

Claims Analysis

Total Claims: 4
Claim 1
Independent Claim 389 words
A method for debugging and testing the correctness of programs with a data processing system provided with at least a first user terminal having display and keyboard and a storage storing a monitoring program, a source program which must be debugged and tested, the source program comprising a plurality of executable instruction rows, and an object program, said object program being generated from said source program by a preprocessing operation which includes in said source program, at each executable row, a call to a control routine, comprising the steps of: activating through said first user terminal first monitoring process based on said monitoring program, and activating a second process executing said object program, said activations occurring in any order, signaling by said second process to said first monitoring process by means of a first message stored in a first message queue the occurrence of the activation of said second process, detecting said first message by said first monitoring process and signalling to said second process with a second message, stored in a second message queue, modes to be followed in the further processing of said second process, wherein said monitoring program comprises a main module and a background module, the activation of said first monitoring process comprising the steps of activating a main monitor process and the further step of activating a background monitor process, said main monitor and background monitor communicating each with the other and with said second process by means of said first message queue, a third message queue and said second message queue, said queues being respectively related to said main monitor, said background monitor and said second process, and wherein said storage stores a test routine (TEST SCRIPT) which must be performed at a predetermined point of said second process, further comprising the steps of identifying said predetermined point, by means of a background break point referring to said test routine in a break point table accessible for read/write operations by said main monitor and background monitor and accessible for read operation by aid second process, detecting by said second process said background break point, and forwarding a message to said background monitor, upon detection of said background break point, and generating and activating by said background monitor a child testing process, based on said test routine referred to by said background break point.
Claim 2
Independent Claim 389 words
A method for debugging and testing the correctness of programs with a data processing system provided with at least a first user terminal having display and keyboard and a storage storing a monitoring program, a source program which must be debugged and tested, the source program comprising a plurality of executable instruction rows, and an object program, said object program being generated from said source program by a preprocessing operation which includes in said source program, at each executable row, a call to a control routine, comprising the steps of: activating through said first user terminal first monitoring process based on said monitoring program, and activating a second process executing said object program, said activations occurring in any order, signaling by said second process to said first monitoring process by means of a first message stored in a first message queue the occurrence of the activation of said second process, detecting said first message by said first monitoring process and signalling to said second process with a second message, stored in a second message queue, modes to be followed in the further processing of said second process, wherein said monitoring program comprises a main module and a background module, the activation of said first monitoring process comprising the steps of activating a main monitor process and the further step of activating a background monitor process, said main monitor and background monitor communicating each with the other and with said second process by means of said first message queue, a third message queue and said second message queue, said queues being respectively related to said main monitor, said background monitor and said second process, and wherein said storage stores a test routine (TEST SCRIPT) which must be performed at a predetermined point of said second process, further comprising the steps of identifying said predetermined point, by means of a background break point referring to said test routine in a break point table accessible for read/write operations by said main monitor and background monitor and accessible for read operation by aid second process, detecting by said second process said background break point, and forwarding a message to said background monitor, upon detection of said background break point, and generating and activating by said background monitor a child testing process, based on said test routine referred to by said background break point.
Claim 3
Dependent Claim 41 words
The method for debugging and testing the correctness of programs of claim 1, wherein said data processing system is provided with a second user terminal having display and keyboard, the activation of said second process being performed through said second terminal.
Claim 4
Dependent Claim 141 words
The method for debugging and testing the correctness of the programs of claim 2, said storage storing at least a second source program to be debugged and tested, and at least a second object program generated from said second source program by a preprocessing which includes at each executable row of said second source program, a call to a control routine, further comprising the steps of: activating a third process executing said third object program, signaling by said third process to said first process, by means of a third message stored in said first message queue of the occurred activation of said third process, and detecting said third message by said first process and signaling to said third process, with a fourth message stored in said second message queue, modes to be followed in the further proceeding of said third process.

References Cited (Backward Citations)

US3707725A Cited
US5142679A Cited
US4750110A Cited
US4589068A Cited
US4811276A Cited
US4937036A Cited
US4859995A Cited
US5038348A Cited

USPTO Annuity & Maintenance Windows

Annuity Stage Window Opens Payment Deadline Surcharge Period Until Estimated Fee Status
3.5 Years (Year 4) 1997-06-06 1997-12-06 1998-06-07 $2000.00 Window Closed / Lapsed
7.5 Years (Year 8) 2001-06-06 2001-12-06 2002-06-07 $3760.00 Window Closed / Lapsed
11.5 Years (Year 12) 2005-06-06 2005-12-06 2006-06-07 $7700.00 Window Closed / Lapsed

Assigned Categories & Tags

No categories assigned to this patent yet.

Assign Category Tag