I raised this question as a github issue: https://github.com/Perl/perl5/issues/19399 The upshot is simple: If we build with that flag, all is fine. If we don't, then any XS code or C library binding to a program that uses the C `putenv()` function will crash with assertion errors at global destruction time: t/30tickit.t .............. 1/? panic: free from wrong pool, 1!=55bca53652a0 during global destruction. t/30tickit.t .............. Dubious, test returned 22 (wstat 5632, 0x1600) All 8 subtests passed Can we just turn this on now? Furthermore, can we get this in in time to test it on 5.35.10 so it's part of 5.36? -- Paul "LeoNerd" Evans leonerd@leonerd.org.uk | https://metacpan.org/author/PEVANS http://www.leonerd.org.uk/ | https://www.tindie.com/stores/leonerd/Thread Next