log-size logical-to-physical
Simics Reference Manual  /  3 Commands  /  3.2 Command List  / 

log-type

Synopsis

log-type [object] [-enable|-disable|-add|-sub] ["log-type"] [-r]
<conf_object>.log-type [-enable|-disable|-add|-sub] ["log-type"] [-r]

Description

Log messages are categorised into one of the several log types. By default, messages of all types are handled in the same way. This command can be used to select one or several types. Only messages of the selected types will be logged and displayed, as defined by the log-level command. The flags -enable and -disable can be used to add and remove a single log type. (The flags -add/-sub are deprecated aliases of -enable/-disable.)

The object argument can be used to apply the change just to a particular object. Please note that when object is specified the log type will be also recursively updated for all descendants of object, whose name matches object.bank[.*], object.port[.*] or object.impl[.*] pattern. The flag -r can be used to operate on all the descendants of the object object.

The log types are Info, Error, Critical, Spec_Violation and Unimplemented. The Info type is used for harmless info or debug messages. Error is used when an error prevents the simulation from running properly; this type does not have any log-level. Critical is used to signal serious errors that a model may not be able to resume from; the simulation is stopped. Spec_Violation is used when a target program runs a command that violates the device specification. And Unimplemented is used when a model does not implement a specific functionality, bit or register.

All types can be enabled by setting log-type to all. It is not possible to disable breaking on Critical.

Provided By

Simics Core

See Also

log, <conf_object>.log-group, log-level, log-size
log-size logical-to-physical