| Prev | Next | Start of Chapter | End of Chapter | Contents | Glossary | Index | Comments | (5 out of 10)

Displaying Trace Messages

During debugging, you might want to display messages in the Operator Logbook that trace each execution as it occurs. This can be helpful for determining whether executions occur and in what order.

By default, G2 does not display trace messages.

To display trace messages:

  1. Edit the Tracing-message-level attribute in the Debugging Parameters system table.

  2. Set the Tracing-and-breakpoints-enabled? attribute in the Debugging Parameters system table to yes.

For information about the available levels of trace messages, see Controlling Debugging Trace Messages.

For example, suppose you have an action button that executes a procedure, which in turn calls another procedure. Setting the tracing message level to level 1 (trace messages on entry and exit) and enabling tracing and breakpoints causes G2 to display trace messages each time G2 begins and finishes executing each procedure, as this picture shows.


This example shows the trace messages that G2 displays each time a variable receives a new value.


This example shows trace messages that G2 displays during rule execution.



Note: Displaying trace messages for an entire knowledge base often creates a backlog of messages. This makes it difficult to display a menu or perform other activities while G2 is providing trace messages.

To stop displaying trace messages, press Control + z. G2 pauses the knowledge base and stops producing trace messages. When you resume, G2 resumes displaying trace messages, until you change settings to tell it not to display trace messages.

| Prev | Next | Start of Chapter | End of Chapter | Contents | Glossary | Index | Comments | (5 out of 10)

Copyright © 1997 Gensym Corporation, Inc.