Informal VM messages may also be enabled/disabled programmatically,
by sending ObjectMemory infoPrinting:
passing a boolean argument;
as in:
or:
ObjectMemory infoPrinting:true
Finally, they may be enabled/disabled initially,
via smalltalk (or application) the command line arguments:
ObjectMemory infoPrinting:false
"--noInfoPrint"
and "--infoPrint"
.
Typical info messages are:
the messages include the VM's subsystem (here: incremental GC or 'IGC' for short)
and the severity (here always: 'info').
IGC [info]: found 17352 bytes of free storage ...
GC [info]: reclaimed 1185 symbols
These VM messages may also be enabled/disabled programmatically,
by sending ObjectMemory debugPrinting:
passing a boolean argument;
as in:
or:
ObjectMemory debugPrinting:true
Finally, they may be enabled/disabled initially,
via smalltalk (or application) the command line arguments:
ObjectMemory debugPrinting:false
"--noDebugPrint"
and "--debugPrint"
.
Error and warning messages include the VM's subsystem and the severity ('warning' or 'error').
These VM messages may also be enabled/disabled programmatically;
as in:
or:
Display class errorPrinting:true
Display class errorPrinting:false
"infoPrint:"
message (implemented in Object
).
If enabled, these are sent to the standard error stream.
These messages can be enabled/disabled programmatically;
as in:
or:
Object infoPrinting:true
Object infoPrinting:false
These messages include the classes name (where the message was generated) and the severity ('info' or 'warning').
Copyright © Claus Gittinger Development & Consulting, all rights reserved