Thanks for the replies.

And just to clarify, I *can* get what I need by correctly using croak/die/confess/warn in the appropriate places or by adding additional details to the actual exception message. This is more a question of DWIW when we mistakenly use croak() in a spot where die() would been more informative.

Here's some example code. And yes, it's completely insecure; it's just to demonstrate the issue.

#!/usr/bin/env perl

{
  package MyModule;

  use strict;
  use warnings;
  use Carp;

  sub a { croak 'croaking' }
  sub b { die 'dying' }

  sub dispatch {
    my $class = shift;
    my $method = shift or croak 'no method name supplied';

    $class->$method;
  }
}

while (<>) {
  chomp;
  next unless /\S/;

  eval { MyModule->dispatch($_) };
  warn $@ if $@;
}
[download]

If you run it and enter 'b', you'll see: "dying at ./try line 11, <> line 2." Line 11 is in fact the b() routine, so that's great.

Now enter 'a' and you get: "croaking at ./try line 25." That is not helpful, since line 25 is just the dispatch routine. We have no idea what was dispatched that raised the error.

So ideally, what I would like to see is the first two call frames of the stack, rather than only the second.

IOW, croak() would emit something like this by default:

croaking at ./try line 12, <> line 1.
	MyModule::a("MyModule") called at ./try line 19

Any thoughts on how to accomplish that?

Thanks!