This appears to be a bug in perl. It looks like the memory where the anonymous string lives is released before the assignment is done, resulting in an invalid memory access. Segfault.

Here's a workaround that relies on increasing the refcount so that underlying memory is not released:

my $temp_value = q(\'/Path/to/log.txt');
my $value = eval $temp_value;  
{
    my $foo = $value;
    $value = $$value;
}

[download]
I'm looking for how to fix perl, but I invite anyone who knows the code better take this and run with it.

After Compline,
Zaxo

In reply to (Zaxo) Re: Bizarre References Question by Zaxo
in thread Bizarre References Question by mpennucci

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.