|log $level, $msg||Log a debug message of the given severity level (0 is highest, higher is less important) to all interested parties.|
|stderr_loglevel $level||Set the loglevel for logging to stderr (defaults to the value of the environment variable PERL_CORO_STDERR_LOGLEVEL, or -1 if missing).|
|session_loglevel $level||Set the default loglevel for new coro debug sessions (defaults to the value of the environment variable PERL_CORO_DEFAULT_LOGLEVEL, or -1 if missing).|
|trace $coro, $loglevel||
Enables tracing the given coroutine at the given loglevel. If loglevel is
omitted, use 5. If coro is omitted, trace the current coroutine. Tracing
incurs a very high runtime overhead.
It is not uncommon to enable tracing on oneself by simply calling Coro::Debug::trace.
A message will be logged at the given loglevel if it is not possible to enable tracing.
|untrace $coro||Disables tracing on the given coroutine.|
|command $string||Execute a debugger command, sending any output to STDOUT. Used by session, below.|
|session $fh||Run an interactive debugger session on the given filehandle. Each line entered is simply passed to command (with a few exceptions).|
|$server = new_unix_server Coro::Debug $path||
Creates a new unix domain socket that listens for connection requests and
runs session on any connection. Normal unix permission checks and umask
applies, so you can protect your socket by puttint it into a protected
The socat utility is an excellent way to connect to this socket:
Socat also offers history support:
The server accepts connections until it is destroyed, so you must keep the return value around as long as you want the server to stay available.
|$server = new_tcp_server Coro::Debug $port||
Similar to new_unix_server, but binds on a TCP port. Note that this is
usually results in a gaping security hole.
Currently, only a TCPv4 socket is created, in the future, a TCPv6 socket might also be created.
Marc A. Lehmann <email@example.com> http://software.schmorp.de/pkg/Coro.html
|perl v5.20.3||DEBUG (3)||2015-10-16|