inviso_rt_meta(3erl) [linux 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)

inviso_lfm_tpfreader(3erl)				     Erlang Module Definition					inviso_lfm_tpfreader(3erl)

NAME

       inviso_lfm_tpfreader - Inviso Standard Reader Process to Standard Logfile Merger

DESCRIPTION

       Implements the standard reader process to the standard logfile merger inviso_lfm .

       The  reader  process reads logfiles belonging to the same set (normally one node) in chronological order and delivers logged trace messages
       one by one to the output process. Before any trace messages are delivered, the inviso_lfm_tpreader implementation reads	the  entire  trace
       information file (if in use) and builds a database over pid-to-alias associations.

       The  inviso_lfm_tpreader  implementation  is capable of considering that an alias may have been used for several processes during different
       times. An alias may also be in use for several pids at the same time, on purpose. If a process has generated a trace message, all  associa-
       tions between that pid and aliases will be presented as the list PidMappings in the message sent to the output process.

EXPORTS

       handle_logfile_sort_wrapset(LogFiles) -> FileList2

	      Types  LogFiles = [{trace_log, FileList}]
		     FileList = FileList2 = [FileName]
		     FileName = string()

	      Only one {trace_log, FileList} tuple is expected in LogFiles , all other tuples are ignored. FileList must:

		* contain one single file name, or

		* a list of wraplog files, following the naming convention <Prefix><Nr><Suffix> .

	      Sorts  the  files  in  FileList  in chronological order beginning with the oldest. Sorting is only relevant if FileList is a list of
	      wraplogs. The sorting is done on finding the modulo-counter in the filename and not on filesystem timestamps.

	      This function is exported for convenience should an own reader process be implemented.

THE TRACE INFORMATION FILE PROTOCOL

       The format of a trace information file is dictated by the meta tracer process. The inviso_lfm_tpfreader implementation of a reader  process
       understands  the  following  trace  information	entries. Note that the inviso_rt_meta trace information file is on binary format prefixing
       every entry with a 4 byte length indicator.

	 {Pid, Alias, alias, NowStamp} :
	   Pid = pid()
	   Alias = term()
	   NowStamp = term() , but in current implementation as returned from erlang:now/0

	   This message indicates that from now on shall Pid be associated with Alias .

	 {MaybePid, Alias, unalias, NowStamp} :
	   MaybePid = pid() | undefined
	   Alias = term()
	   NowStamp = term() , see above

	   This message indicates that, if MaybePid is a pid, this pid shall no longer be associated with Alias . If it is undefined , all associ-
	   ations with Alias from now shall be considered invalid.

	   Also  note  that  there  are many situations where unalias entries will be missing. For instance if a process terminates without making
	   explicit function calls removing its associations first. This is seldom a problem unless the pid is reused.

Ericsson AB							   inviso 0.6.2 					inviso_lfm_tpfreader(3erl)