Bug#779357: perl: Debugger hangs when threads are involved
Niko Tyni
ntyni at debian.org
Sat Feb 28 18:01:58 UTC 2015
forwarded 779357 https://rt.perl.org/Public/Bug/Display.html?id=120170
thanks
On Fri, Feb 27, 2015 at 05:15:57PM -0500, James McCoy wrote:
> As an FYI, upstream commit cde405a6b is what caused "perl -dt" to be
> required. Re-adding the lock prototype to the current perl5db.pl allows
> "perl -d" to at least start, but then the debugger errors out with
> "Modification of a read-only value attempted at .../perl5db.pl line
> 4129." which is this:
>
> # Save current single-step setting.
> $stack[-1] = $single;
Thanks. I got that far too, and I also bisected the 'Modification of a
read-only value' thing to ce0d59fdd1c7d145efdf6bf8da56a259fed483e4
but that doesn't help much.
I note this is already reported upstream as
https://rt.perl.org/Public/Bug/Display.html?id=120170
(unfortunately with no action since 2013), and very recently also
against the 'threads' distribution at
https://rt.cpan.org/Public/Bug/Display.html?id=102406
--
Niko Tyni ntyni at debian.org
More information about the Perl-maintainers
mailing list