It isn't just that $@ is getting blown away, is it? Maybe change 
eval { throw TestCaller };
isa_ok($@, 'TestCaller');

is_deeply($@->...

[download]
to 
eval { throw TestCaller };
my $error = $@;
isa_ok($error, 'TestCaller');

is_deeply($error->...

[download]
And see if that makes any difference at all? Just a thought. Still, you ideally wouldn't want Devel::Cover to alter your program in any way. 
------------
:Wq
Not an editor command: Wq

[download]

In reply to Re: Devel::Cover eating caller() information by etcshadow
in thread Devel::Cover eating caller() information by stvn

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.