Beechbone has asked for the wisdom of the Perl Monks concerning the following question:

I think I could do it myself, but maybe someone already has the solution ready?...:

I'd need a debugger backend to log all calls to a specific object, ideally as executable Perl code.

XY-problem? A CPAN module I use behaves very badly when used with a specific parameter in my program. I want to create a test case for the bug report. But, there are dozens of calls to that object, executed hundreds of times in complex logic---manually rolling that into a test case without sending my whole program and about 130GB of data it works on would take ages.


Search, Ask, Know
  • Comment on db backend for logging all calls to a class

Replies are listed 'Best First'.
Re: db backend for logging all calls to a class
by Bloodnok (Vicar) on Mar 10, 2009 at 13:57 UTC
    Could you not use Lof::Log4Perl to your advantage - by instrumenting calls etc. ?

    A user level that continues to overstate my experience :-))
Re: db backend for logging all calls to a class
by weismat (Friar) on Mar 10, 2009 at 12:40 UTC
    Have a look at Memoize::Storable.
    Only question is if your class can be memoized or not - otherwise I would consider to look at the mechanism used to write your own memoizer without caching...
Re: db backend for logging all calls to a class
by clueless newbie (Curate) on Mar 10, 2009 at 15:11 UTC
    Would Conway's Hook::LexWrap on CPAN do what you want?