Here's an artificially simple program that will crash your computer. (It crashed mine anyways!) 
use strict;
use warnings;

sub_1();
sub_2();

sub sub_1 {
    my $hash = {};
    $hash->{$_}=1 for 1 .. 10;
}

sub sub_2 {
    my $hash = {};
    $hash->{$_}=1 for 1 .. 10000000;
}

[download]
UPDATE: I guess this just isn't possible without using old fasioned elbow grease. In this case obviously you can see the problem by eyeballing it, but in the wilderness these problems tend to be better hidden. Could the masters of perl -d or Devel::* or whatever tool share how they would trick out the fact that

-- sub_2 is the problem
-- $hash in sub_2 is the more specific problem

Much obliged!

UPDATE: Well, I guess it's just not possible.

UPDATE 2: No, you can't have a pony (scroll to the bottom for a picture of the pony :(

In reply to How would you use perl debugging tools to pinpoint the problem here? by tphyahoo

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.