Hi,

if you have some terminal scroll back functionality in your debugger session, you could just set the first parameter to something greater 1 (depending on how deep you want to dive in)
x 10 grep {$_->{CHIPS_PART_NAME}=~/gravity/i} @goodRefDes
or leave it out to get the full hierarchy:
x grep {$_->{CHIPS_PART_NAME}=~/gravity/i} @goodRefDes

If you want to filter further either add one more grep expression,
x grep {more filtering...} grep {$_->{CHIPS_PART_NAME}=~/gravity/i} @goodRefDes
or if the order of hash entries is meaningful, accessing the array by indexing is another option, eg. access the last entry.
x (grep {$_->{CHIPS_PART_NAME}=~/gravity/i} @goodRefDes)[-1]

Hope that helps.

In reply to Re: examining HASH(0x1234567) in Debugger by hexcoder
in thread examining HASH(0x1234567) in Debugger by boleary

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.