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

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?

Replies are listed 'Best First'.
Re^9: Tracking down an Lvalue bug?
by ikegami (Patriarch) on Mar 21, 2012 at 02:01 UTC
    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