Ports Search

Jonk is simple job tanking system. Job is saved and taken out. Besides, nothing is done. You may use Jonk to make original Job Queuing System.

Provides shared memory structures (using memory mapped files via IPC::Mmap) to be used by diagnostic and debugger applications for Perl scripts (see Devel::STrace). Using XS/C code to maximize performance, creates a set of ring buffers with a configurable number of slots. Each slot includes a field for a line number, a timestamp, and a fully qualified subroutine name. Each ring buffer also includes additional headers and fields to support diagnostic interfaces, e.g., watched expressions, command/response interfaces to the monitored applications, etc.

Provides a strace/truss-like runtime call monitor for Perl applications. Note that, while strace/truss only dumps system calls, Devel::STrace dumps all calls to Perl subs on the application's stack. Also note that Devel::STrace cannot trace non-Perl calls (e.g., calls inside XS/C modules), so an additional external strace/truss monitor may be needed to fully diagnose a misbehaving Perl script.

This module can be used to more easily spot the place where a program or a module generates errors. Its use is extremely simple, reduced to just'use'ing it. This is achieved by modifying the functions warn() and die() in order to replace the standard messages by complete stack traces that precisely indicates how and where the error or warning occurred. Other than this, their use should stay unchanged, even when using die() inside eval().

The Devel::StackTrace module contains two classes, Devel::StackTrace and Devel::StackTraceFrame. The goal of this object is to encapsulate the information that can found through using the caller() function, as well as providing a simple interface to this data. The Devel::StackTrace object contains a set of Devel::StackTraceFrame objects, one for each level of the stack. The frames contain all the data available from caller() as of Perl 5.6.0 though this module still works with 5.00503.

This module lets you add debugging instructions which look like comments and do nothing unless you 'use' this module. use Devel::StealthDebug; my $foo = 0; # ... Several processing on $foo my $bar = 1 / $foo; #!assert($foo != 0)! my %myhash; #!watch(%myhash)! sub func1 { #!emit(Entering func1)! #... }

Exception::Handler Exception::Handler helps to report exceptions with formatted text call-stack.

Devel::TraceUse - Show the modules your program loads, recursively. An apparently simple program may load a lot of modules. That's useful, but sometimes you may wonder exactly which part of your program loads which module. Devel::TraceUse can analyze a program to see which part used which module.

Device::USB, Perl wrappers for libusb.

This module serves as an easy, clean alternative to Exporter. Unlike Exporter, it is not subclassed, but it simply exports a custom import() into your namespace. With Exporter::Tidy, you don't need to use any package global in your module. Even the subs you export can be lexically scoped.