SYNOPSIS

    use Devel::StackTrace::WithLexicals;

    my $trace = Devel::StackTrace::WithLexicals->new;
    ${ $trace->frame(1)->lexical('$self') }->oh_god_why();

DESCRIPTION

Devel::StackTrace is pretty good at generating stack traces.

PadWalker is pretty good at the inspection and modification of your callers' lexical variables.

Devel::StackTrace::WithLexicals is pretty good at generating stack traces with all your callers' lexical variables.

METHODS

All the same as Devel::StackTrace, except that frames (in class Devel::StackTrace::WithLexicals::Frame) also have a \*(C`lexicals\*(C' method. This returns the same hashref as returned by PadWalker.

If the \*(C`no_refs\*(C' option to Devel::StackTrace is used, then each reference is stringified. This can be useful to avoid leaking memory.

Simple, really.

AUTHOR

Shawn M Moore, \*(C`[email protected]\*(C'

BUGS

I had to copy and paste some code from Devel::StackTrace to achieve this (it's hard to subclass). There may be bugs lingering here.

COPYRIGHT AND LICENSE

Copyright 2008-2009 Shawn M Moore.

Some portions written by Dave Rolsky, they belong to him.

This program is free software; you can redistribute it and/or modify it under the same terms as Perl itself.