System and method for cross-triggering a software logic analyzer and a hardware analyzer

• US 5,611,044 A
• Filed: 04/10/1995
• Issued: 03/11/1997
• Est. Priority Date: 11/01/1993
• Status: Expired due to Term

• Current Assignee: Hewlett-Packard Development Company, L.P. (HP Inc.)
• Original Assignee: Hewlett-Packard Company (HP Inc.)
• Inventors: Lundeby, Bruce A.
• Primary Examiner(s): Beausoliel, Jr., Robert W.
• Assistant Examiner(s): Wright, Norman M.
• Application Number:
  US08/419,651
• Time in Patent Office: 701 Days
• Field of Search: 395/183.04, 395/700, 395/183.01, 395/184.01, 395/183.15, 395/183.14, 395/183.13
• US Class Current: 714/38.11
• CPC Class Codes: G06F 11/25 Testing of logic operation, e.g. by logic analysers
• CPC Class Codes: G06F 11/3466 Performance evaluation by tracing or monitoring

Abstract

A system and method provides software logic analysis of computer system problems. The system and method incorporates event triggering, event limiting and cross-triggering in a software event logging process. A cross-trigger port is provided to facilitate connection between the present system and an external analyzer, such as a hardware logic analyzer or an oscilloscope. An end-user controls the event logging process via a user interface that permits the end-user to write trigger and limit conditions. One embodiment of the present system and method involves the small computer system interface (SCSI) sub-system.

Claims

1. A software logic analyzer for aiding an end-user in the analysis of software problems occurring in a software process residing in a computer system, the analyzer comprising:

an event log;

a kernel log machine, the kernel log machine collects at least one predetermined log point located within the software process, the kernel log machine places said at least one predetermined log point in the event log;

a kernel log machine interface, connected to the kernel log machine, the interface provides the end-user a capability to control the kernel log machine;

decoding means for transforming the event log from a first format to a second format; and

a cross-trigger port having first and second ends, the first end connected to the kernel log machine, the second end connected to an external analyzer.

2. The software logic analyzer as recited in claim 1, wherein the cross-trigger port is bi-directional.

3. The software logic analyzer as recited in claim 2, wherein the cross-trigger port resides within an I/O interface of the computer system.

4. The software logic analyzer as recited in claim 3, wherein the cross-trigger port can be configured as a trigger input port, the trigger input port providing the external analyzer a capability to arm the software logic analyzer.

5. The software logic analyzer as recited in claim 3, wherein the cross-trigger port can be configured as a trigger input port, the trigger input port providing the external analyzer a capability to trigger the software logic analyzer.

6. The software logic analyzer as recited in claim 3, wherein the cross-trigger port can be configured as a trigger output port, the trigger output port providing the software logic analyzer a capability to send a message to the external analyzer.

7. The software logic analyzer as recited in claim 3, wherein the external logic analyzer is a hardware logic analyzer.

8. The software logic analyzer as recited in claim 3, wherein the external logic analyzer is an oscilloscope.

9. The software logic analyzer as recited in claim 3, wherein the kernel log machine is located in a first area of memory, the first area being inaccessible by the end-user.

10. The software logic analyzer as recited in claim 9, wherein the I/O interface comprises a SCSI interface.

11. The software logic analyzer as recited in claim 10, wherein the SCSI drive is controlled by the software process, the at least one predetermined log point indicative of a sub-process of the SCSI interface.

12. A method for software logic analysis of problems occurring in a software process, the method comprising the steps of:

(a) starting an analyzer function to collect data located in the software process upon encountering a predetermined log point located within the software process, the analyzer function having an operation state;

(b) determining whether an external trigger condition has been satisfied; and

(c) saving a first predetermined log point in an event log when the external trigger condition is satisfied.

13. The method as recited in claim 12, wherein step (b) further comprises the steps of:

(b1) determining whether the operation state is equal to ARMED;

(b2) determining, if the operation state is equal to ARMED, whether the external trigger condition has been satisfied; and

(b3) resetting the operation state equal to NOT_-- ARMED if the external trigger condition has been satisfied.

14. The method as recited in claim 13, further comprising the steps of:

(d) determining, if the operation state is not equal to ARMED after step (b1), whether an internal trigger condition is present;

(e) determining, if the internal trigger condition is present, whether the internal trigger condition has been satisfied;

(f) setting the operation state of the analyzer function equal to TRIGGERED if the internal trigger condition has been satisfied;

(g) saving a second predetermined log point in an event log.