Ok, I can clear the warning.
No upstream problem.
Devel::PeekPoke writes to buffers manually via substr, but got the
logic with new cases with certain COW strings wrong. (len >= 10)
5.20.1 is good to go.
Just Devel::PeekPoke::PP needs to adjust to COW, it cannot even detect
COW strings in its current API.
I'm working on it. (easy in XS but hard with PP)
On Wed, Sep 10, 2014 at 6:28 AM, Reini Urban <rurban@cpan.org> wrote:
Show quoted text> I suspect a serious upstream regression in destructive substr handling
> with certain string lengths 10-14. (which is incidently exactly the
> area I tried to fix earlier)
>
> This is a normal pure-perl substr, which is failing in certain string lengths.
>
> See
https://github.com/rurban/Devel-PeekPoke/commit/8099054c964dd0a62805f27be06bbe49bbe7f452
>
> Please hold 5.20.1 until this is analyzed.
>
> On Wed, Sep 10, 2014 at 12:22 AM, Peter Rabbitson via RT
> <bug-Devel-PeekPoke@rt.cpan.org> wrote:
>> Queue: Devel-PeekPoke
>> Ticket <URL:
https://rt.cpan.org/Ticket/Display.html?id=98745 >
>>
>> On 09/10/2014 07:14 AM, Slaven_Rezic via RT wrote:
>> Sigh. Yes, reproduced locally. I will not be able to look at this for at
>> least 1.5 weeks. This is still a low-prio module, so I am content with
>> it languishing (like it did during 0.03). It is due for a thorough
>> re-gut anyway.
>>
>> If someone else beats me to diagnosing the 5.20 intermittent fail - it's
>> be grand ;)