Doesn't your initial explanation imply that we uncovered a bug? die doesn't correct the stack trace properly when called within an eval. If a recent update involves the ineval() method, that would explain why the die method use to work until the admin guy updated the module. Anyway, try this code segment. I left work early today, but I was able to recreate the problem on my machine at home.

#!/usr/bin/perl

use strict;
use CGI::Carp qw(fatalsToBrowser warningsToBrowser);

eval {
die "Ouch";
};
if ($@) {
    print $@, "\n";
}

eval {
my_die("Ouch");
};
if ($@) {
    print $@, "\n";
}

sub my_die {
  my ($arg) = @_;

  if (CGI::Carp::ineval) {
    $arg = join("", @_);
    my($file,$line,$id) = CGI::Carp::id(1);
    $arg .= " at $file line $line." unless $arg=~/\n$/;
    if ($arg !~ /\n$/) {
      $arg .= "\n";
    }
    CGI::Carp::realdie $arg;
  }
  if (!ref($arg)) {
    $arg = join("", @_);
    my($file,$line,$id) = CGI::Carp::id(1);
    $arg .= " at $file line $line." unless $arg=~/\n$/;
    &fatalsToBrowser($arg) if $CGI::Carp::WRAP;
    if (($arg =~ /\n$/) || !exists($ENV{MOD_PERL})) {
      my $stamp = CGI::Carp::stamp;
      $arg=~s/^/$stamp/gm;
    }
    if ($arg !~ /\n$/) {
      $arg .= "\n";
    }
  }
  realdie $arg;
}
[download]