If configured with PatternLayout, Log::Log4perl will use Perl's caller($depth) function internally to obtain the name of the function/method where the logging statement is located in at runtime.

Since caller($depth) returns "(eval)" as the subroutine name if you're within an eval {}, Log::Log4perl will display "(eval)".

There's a nasty trick you could use to bump up the caller level and have it return the calling function:
use Log::Log4perl qw(:easy); Log::Log4perl->easy_init( { level => $DEBUG, layout => "%M: %m%n", }); foo(); sub foo { eval { local $Log::Log4perl::caller_depth = $Log::Log4perl::caller_depth + 1; DEBUG("I'm here!"); }; }
This will print
main::foo: I'm here!
as expected. However, there's several things to consider: Check the log4perl-devel@lists.sourceforge.net mailing list for updates.

In reply to Re: Log4Perl Naming an Eval by saintmike
in thread Log4Perl Naming an Eval by set_uk

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":



  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.