i
Module
Module Summary
Description
The i module provides short forms for some of the functions used by the graphical Debugger and some of the functions in module int, the Erlang interpreter.
This module also provides facilities for displaying status information about interpreted processes and break points.
It is possible to attach to interpreted processes by giving the corresponding process identity only. By default, an attachment window is displayed. Processes at other Erlang nodes can be attached manually or automatically.
By preference, these functions can be included in module shell_default. By default, they are included in that module.
Exports
Starts a new graphical monitor. This is the Monitor window, the main window of Debugger. All the Debugger and interpreter functionality is accessed from the Monitor window. This window displays the status of all processes that have been or are executing interpreted modules.
ii(AbsModules) -> ok
ii(AbsModule) -> {module, Module} | error
ini(AbsModules) -> ok
ini(AbsModule) -> {module, Module} | error
Types
Interprets the specified module(s). ii/1 interprets the module(s) only at the current node, see int:i/1. ini/1 interprets the module(s) at all known nodes, see int:ni/1.
iq(AbsModule) -> ok
inq(AbsModule) -> ok
Types
Stops interpreting the specified module. iq/1 stops interpreting the module only at the current node. inq/1 stops interpreting the module at all known nodes.
Makes a printout of all interpreted modules. Modules are printed together with the full path name of the corresponding source code file.
Prints the current status of all interpreted processes.
Clears information about processes executing interpreted code by removing all information about terminated processes.
iaa(Flags) -> true
iaa(Flags, Function) -> true
Types
Sets when and how to attach to a debugged process automatically, see int:auto_attach/2. Function defaults to the standard function used by Debugger.
Types
Sets how to save call frames in the stack, see int:stack_trace/1.
Types
Attaches to the debugged process Pid. An Attach Process window is opened for the process.
Types
Same as ia(Pid), where Pid is the result of calling the shell function pid(X,Y,Z).
ia(Pid, Function) -> ok | no_proc
Types
Attaches to the debugged process Pid. The interpreter calls spawn(Module, Name, [Pid]) (and ignores the result).
ia(X,Y,Z, Function) -> ok | no_proc
Types
Same as ia(Pid, Function), where Pid is the result of calling the shell function pid(X,Y,Z). An attached process is expected to call the unofficial function int:attached(Pid) and to be able to handle messages from the interpreter. For an example, see dbg_wx_trace.erl.
ib(Module, Line) -> ok | {error, break_exists}
Types
Creates a breakpoint at Line in Module.
ib(Module, Name, Arity) -> ok | {error, function_not_found}
Types
Creates breakpoints at the first line of every clause of function Module:Name/Arity.
Deletes all breakpoints.
Types
Deletes all breakpoints in Module.
Types
Deletes the breakpoint at Line in Module.
ir(Module, Name, Arity) -> ok | {error, function_not_found}
Types
Deletes the breakpoints at the first line of every clause of function Module:Name/Arity.
Types
Makes the breakpoint at Line in Module inactive.
Types
Makes the breakpoint at Line in Module active.
iba(Module, Line, Action) -> ok
Types
Sets the trigger action of the breakpoint at Line in Module to Action.
ibc(Module, Line, Function) -> ok
Types
Sets the conditional test of the breakpoint at Line in Module to Function.
The conditional test is performed by calling Module:Name(Bindings), where Bindings is the current variable bindings. The function must return true (break) or false (do not break). To retrieve the value of a variable Var, use int:get_binding(Var, Bindings).
Prints all existing breakpoints.
Types
Prints all existing breakpoints in Module.
Returns the current version number of the interpreter. Same as the version number of the Debugger application.
Prints help text.