STDLIB(7) Erlang Application Definition STDLIB(7)NAME
STDLIB - The STDLIB Application
DESCRIPTION
The STDLIB is mandatory in the sense that the minimal system based on Erlang/OTP consists of Kernel and STDLIB. The STDLIB application con-
tains no services.
CONFIGURATION
The following configuration parameters are defined for the STDLIB application. See app(5) for more information about configuration parame-
ters.
shell_esc = icl | abort :
This parameter can be used to alter the behaviour of the Erlang shell when ^G is pressed.
restricted_shell = module() :
This parameter can be used to run the Erlang shell in restricted mode.
shell_catch_exception = bool() :
This parameter can be used to set the exception handling of the Erlang shell's evaluator process.
shell_history_length = integer() >= 0 :
This parameter can be used to determine how many commands are saved by the Erlang shell.
shell_prompt_func = {Mod, Func} | default :
where
* Mod = atom()
* Func = atom()
This parameter can be used to set a customized Erlang shell prompt function.
shell_saved_results = integer() >= 0 :
This parameter can be used to determine how many results are saved by the Erlang shell.
SEE ALSO app(5) , application(3erl) , shell(3erl) ,
Ericsson AB stdlib 1.17.3 STDLIB(7)
Check Out this Related Man Page
inviso_rt_meta(3erl) Erlang Module Definition inviso_rt_meta(3erl)NAME
inviso_rt_meta - Direct API to the Inviso Runtime Component's meta tracer
DESCRIPTION
This module provides a direct API to the inviso meta tracer. These functions are only meant to be used in meta tracing CallFunc and Remove-
Func .
It can sometimes be necessary to manipulate meta match-patterns from CallFunc s and RemoveFunc s. The problem then is that call-funcs and
remove-funcs are meta trace call-backs executed inside the inviso meta tracer's context. Hence making calls to the regular API's manipulat-
ing meta trace-patterns will hang the inviso meta tracer!.
To remedy this problem, a number of useful tpm-functions are available in this API. It must be understood that their actions are local to
the Erlang node where they are called.
EXPORTS
tpm_ms(Mod,Func,Arity,MSname,MS) -> {ok,0} | {ok,1} | {error,not_initiated}
See inviso:tpm_ms/6 for details. Note that this function only effects meta trace-patterns on the Erlang node where the function is
called. This also implies that only the local inviso meta tracer's name-database is updated with MSname .
tpm_ms_tracer(Mod,Func,Arity,MSname,MS) -> {ok,0} | {ok,1} | {error,not_initiated}
See inviso:tpm_ms_ms/6 for details. Note that this function only effects meta trace-patterns on the Erlang node where the function
is called. This also implies that only the local inviso meta tracer's name-database is updated with MSname .
list_tpm_ms(Mod,Func,Arity) -> [MSname]
Returns a list of all MSname in use for Mod:Func/Arity . This can be useful instead of having to have an own-implemented database
over currently in use meta match-functions for a particular function.
ctpm_ms(Mod,Func,Arity,MSname) -> ok
See inviso:ctpm_ms/5 for details. Note that this function only effects meta trace-patterns on the Erlang node where the function is
called. This also implies that only the local inviso meta tracer's name-database is updated with MSname .
get_tracer() -> Tracer
Types Tracer = pid() | port()
Returns the pid or port acting as the receiver of regular trace messages. This is useful if it is necessary to manipulate meta
trace-patterns by hand (using erlang:trace_pattern/3 ) and the {tracer,Tracer} must be used in one of the match-function bodies.
Ericsson AB inviso 0.6.2 inviso_rt_meta(3erl)