in reply to Re^2: To each() their own
in thread To each() their own

nothing is actually broken in my opinion.

Famous last words. If all was sane, there would be no odd behaviour. I think that it is not necessary that the XS code itself uses each. It suffices that somewhere outside a hash reference is iterated, and XS code does something to this hashref passed into the XS which triggers hv_iternext_flags (defined in embed.h) or Perl_hv_iternext_flags perhaps via some macro.

Lets see...

qwurx [shmem] .../build/perl-5.25.10> grep hv_iternext_flags *.c *.h hv.c: while ((entry = hv_iternext_flags(ohv, 0))) { hv.c: while ((entry = hv_iternext_flags(ohv, 0))) { hv.c:=for apidoc hv_iternext_flags hv.c:Perl_hv_iternext_flags(pTHX_ HV *hv, I32 flags) hv.c: HE * const he = hv_iternext_flags(hv, 0); hv.c: while ((entry = hv_iternext_flags(hv, HV_ITERNEXT_WANTPLACEHO +LDERS))) { mathoms.c: return hv_iternext_flags(hv, 0); mro_core.c: /* This is partly based on code in hv_iternext_flags. W +e are not call- perl.c: while ((entry = hv_iternext_flags(dups, 0))) { perlmini.c: while ((entry = hv_iternext_flags(dups, 0))) +{ regcomp.c: while ( (temphe = hv_iternext_flags(hv,0)) ) { regcomp.c: while ( (temphe = hv_iternext_flags(hv,0)) ) { embed.h:#define hv_iternext_flags(a,b) Perl_hv_iternext_flags(aTHX_ + a,b) hv.h:/* Flags for hv_iternext_flags. */ hv.h:#define hv_iternext(hv) hv_iternext_flags(hv, 0) proto.h:PERL_CALLCONV HE* Perl_hv_iternext_flags(pTHX_ HV *hv, I32 +flags)

So hv.c mathoms.c perl.c mro_core.c regcomp.c are possible candidates. Since you also speak of a memory leak loosely coupled with your issue caused by the RE compiler, I'd start looking for code that calls functions from regcomp.c - but that's all just guesswork.

update:

This basic XS (created with h2xs -A Foo)

/* file Foo.xs */ #define PERL_NO_GET_CONTEXT #include "EXTERN.h" #include "perl.h" #include "XSUB.h" #include "ppport.h" MODULE = Foo PACKAGE = Foo SV * foo(hv) HV * hv CODE: hv_store(hv,"newkey", 6, newSVpv("foo", 3),0);

which just adds/updates a key/value pair to a passed hash reference reports the place where Foo::foo($h) is called:

use blib; use Foo; use Data::Dump qw(dd); $h = {foo => 1, bar => 2}; while (($k,$v) = each %$h) { Foo::foo($h) if $k eq 'foo'; } dd $h; __END__ Use of each() on hash after insertion without resetting hash iterator +results in undefined behavior, Perl interpreter: 0x224f010 at foo.pl +line 6. { bar => 2, foo => 1, newkey => "foo" }

Without knowing what perl XS modules you are using inside your application, there's no way to tell where the error would arise from.

perl -le'print map{pack c,($-++?1:13)+ord}split//,ESEL'

Replies are listed 'Best First'.
Re^4: To each() their own
by Ancient.Wizard (Novice) on May 02, 2017 at 19:44 UTC
    yes I agree that that was a bit vague. What I actually wanted to state was that assuming Perl is not broken for some other reason that the behavior of each() whatever it may be for a given circumstance under the condition of being called after an insert into the has is okay by me, I.E. I can live the possibly random pair of key/value returned.
      What I actually wanted to state was that assuming Perl is not broken for some other reason that the behavior of each()

      Perl is not broken here, and the documentation has a warning about inserting hash tuples whilst iterating. As I wrote, per evidence from the source, this warning is only triggered if perl is compiled with PERL_HASH_RANDOMIZE_KEYS. This doesn't mean that such operation is safe for versions that don't emit this warning.

      And ceterum censeo that XS code not being able to propagate their file/lineno to perl internals is, if not a bug, an annoying lack of a basic feature that the XS subsystem should provide. (update: but see update to Re^3: To each() their own)

      perl -le'print map{pack c,($-++?1:13)+ord}split//,ESEL'