- COMPONENT OVERVIEW
- EVENT STRUCTURE
- COPYRIGHT AND LICENCE
Devel::Events - Extensible instrumentation framework
use Devel::Events::Generator::Foo; use Devel::Events::Handler::Bar; use Devel::Events::Filter::Blort; my $h = Devel::Events::Generator->new( handler => Devel::Event::Filter->new( handler => Devel::Events::Handler::Bar->new(), ), );
Devel::Events is an event generation, filtering and analaysis framework for instrumenting and auditing perl code.
The design's purpose is to decouple the mechanics of code instrumentation from the analysis, making it easier to write debugging/profiling tools.
Devel::Events::Generator object fire events, which can be mangled by Devel::Event::Filter objects. Eventually any number of Devel::Event::Handler objects can receive a given event, and perform analysis based on it.
For example Devel::Event::Handler::ObjectTracker can be used to detect leaks.
There are two main types of components - generators and handlers.
Filters are special types of handlers that always delegate to another handler.
The multiplex handler may be used to delegate to any number of handlers, and can be the handler for several generators.
Using these basic components complex chains of handlers can be built to properly analyze the events you are interested in.
object_destroyevents by overriding
CORE::GLOBAL::blessand tracking every object using Variable::Magic.
Uses the perl debugger hook to generate
executing_lineevent for every line using the perl debugger hook.
Fires events for
requireand c<use> calls.
Repeat events to multiple handlers.
Make a handler object out of a callback.
Log all events to an array.
Provides filtering and slicing methods to ease analysis.
object_destroyevents (as generated by Devel::Events::Generator::Objects) to track the lifetime of objects. When objects lifetimes extend beyond the scope they're supposed to be destroyed in leaks can be detected.}
Add various stamp data (time, process ID, thread ID if threads are loaded) to events.
Stringify (by default using "StrVal" in overload, to avoid side effects) all event data to avoid leaking.
Add size reports to events using Devel::Size
Remove certain fields from events.
warn "@event"before delegating to the sub handler. Useful for debugging handler chains.
All events are passed as lists.
The default components will generate lists containing a single string which is the event name, and then a list of key/value pairs.
יובל קוג'מן (Yuval Kogman) <email@example.com>
Karen Etheridge <firstname.lastname@example.org>
This software is copyright (c) 2007 by יובל קוג'מן (Yuval Kogman).
This is free software; you can redistribute it and/or modify it under the same terms as the Perl 5 programming language system itself.