in reply to Re^6: Tracking down an Lvalue bug?
in thread Tracking down an Lvalue bug?

The fix has no effect on: 

my $ref;
{
    my $string = "123";
    $ref = \substr $string, 1, 1;
}

## This was the (IMO false) "bug" scenario.

[download]

The fix is for: 

{
    my $string = "123";
    my $ref = \substr $string, 1, 1;
}

[download]

All the patch does (or is suppose to do) is avoid saving the SV inside of the OP, something that causes $string until the end of the program in the second snippet.

Do you have a way of automating the test so I can use git bisect to find when the behaviour changed (if it did).

Replies are listed 'Best First'.
Re^8: Tracking down an Lvalue bug?
by BrowserUk (Patriarch) on Mar 21, 2012 at 01:56 UTC
    Do you have a way of automating the test

    Is a windows solution suitable?

    With the rise and rise of 'Social' network sites: 'Computers are making people easier to use everyday'
    Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
    "Science is about questioning the status quo. Questioning authority".
    In the absence of evidence, opinion is indistinguishable from prejudice.

    The start of some sanity?
[reply]
      No, not only have I've never built Perl on Windows, I doubt Porting/bisect.pl will work there. In fact, even using modules is problematic. I guess I should start by manually checking the releases around my lvalue patch.
[reply]

        Then, how about using /dev/mem or whatever (it is called) to check the memory consumption? That's all that is required.

        With the rise and rise of 'Social' network sites: 'Computers are making people easier to use everyday'
        Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
        "Science is about questioning the status quo. Questioning authority".
        In the absence of evidence, opinion is indistinguishable from prejudice.

        The start of some sanity?
[reply]

In Section Seekers of Perl Wisdom