As already noted, CGI::Carp will do exactly what you asked for, but...

Consider carefully the wisdom of doing so. Many of us don't use CGI::Carp on sites which will be exposed to the public because detailed information about how and why the code failed could be very helpful to an attacker who wished to compromise the site by deliberately causing it to fail and, perhaps, even help him engineer the means to cause it to fail in a specific manner for his advantage.

CGI::Carp is a handy development tool (especially when you don't have direct access to the server logs), but you'd probably be better off using a more verbose construct which lets you tell the user information which is both safe for you and useful for him¹. Maybe even recover from the error and go on instead of dying. Something like:

unless (my $address = retrieve("/tmp/$session_file")) {
  warn "no session file $!\n";
  create_new_session_file("/tmp/$session_file");
  redirect_user_to('new_session_page');
}
[download]

¹ OK, so the user knows there his session file should have been at /tmp/blahblahblah. What can he do about it and how does this knowledge benefit him in any (legitimate) way?