OK, so others have pointed out the 
@path_detail = [];

[download]
issue, so I won't mention it again :)

I'm not terribly enamoured with your use of @path_details in any event. Your ultimate goal is to place this into the %$rec hash (as a reference) and then save the hash refs in @timing_paths. That's OK, but it would be clearer to me if you said something like 

$rec->{path_details} = [];

[download]
after creating/resetting the $rec hash ref, and then using that straightaway as your array ref when using push: 
push @{ $rec->{path_details} }, $_;

[download]
Now you are being explicit about when/where this info is going to be stored, rather than creating this "artificial" @path_details and then plugging it into $rec->{'path_details'} later.

In reply to Re: references hashes arrays fun ... again :-( by snax
in thread references hashes arrays fun ... again :-( by diarmuid

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.