Hi Gregor, On Tue, Mar 21, 2017 at 1:36 PM, gregor herrmann <gre...@debian.org> wrote: > On Tue, 21 Mar 2017 13:31:32 +0100, gregor herrmann wrote: > >> > This looks like a problem in perl itself possibly causing random crashes >> > elsewhere, too. >> Does this problem also show up with 5.24.1-1 in testing and/or >> 5.24.1-2 in unstable?
Yes, in every later version. I chose the first version BTS knew about. > Looking at the upstream ticket at > https://rt.cpan.org/Public/Bug/Display.html?id=109852 > it seems that the segfaults started with perl 5.23.x, that a perl bug > was fixed in 5.24.0, and that nama still segfaults. -- So not sure > where the problem lies; my guess would be nama. As I read the report there have been numerous fixes after the following commit: https://github.com/Perl/perl5/commit/a5f48505593c7e1ca478de383e24d5cc2541f3ca re-implement OPpASSIGN_COMMON mechanism This commit almost completely replaces the current mechanism for detecting and handing common vars in list assignment, e.g. ... It looks like not all regression are fixed after the re-implementation and the one affecting nama is one of them. I think it should be impossible to trigger an internal assertion in Perl with pure Perl code like nama. Cheers, Balint > > > Cheers, > gregor > > -- > .''`. https://info.comodo.priv.at/ - Debian Developer https://www.debian.org > : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D 85FA BB3A 6801 8649 AA06 > `. `' Member of VIBE!AT & SPI, fellow of the Free Software Foundation Europe > `- BOFH excuse #407: Route flapping at the NAP. -- -- Balint Reczey Debian & Ubuntu Developer