From ae6b6b71cdbfb3fb6e1192178fa1e530a2f07ece Mon Sep 17 00:00:00 2001 From: Tomasz Konojacki Date: Tue, 19 Apr 2022 16:41:23 +0200 Subject: make PERL_USE_SAFE_PUTENV the default and the only option Now environ isn't owned by Perl and calling setenv/putenv in XS code will no longer result in memory corruption. Fixes #19399 --- INSTALL | 15 --------------- 1 file changed, 15 deletions(-) (limited to 'INSTALL') diff --git a/INSTALL b/INSTALL index a4bf4022fc..56080204b2 100644 --- a/INSTALL +++ b/INSTALL @@ -637,21 +637,6 @@ architecture-dependent library for your -DDEBUGGING version of perl. You can do this by changing all the *archlib* variables in config.sh to point to your new architecture-dependent library. -=head3 Environment access - -Perl often needs to write to the program's environment, such as when -C<%ENV> is assigned to. Many implementations of the C library function -C leak memory, so where possible perl will manipulate the -environment directly to avoid these leaks. The default is now to perform -direct manipulation whenever perl is running as a stand alone interpreter, -and to call the safe but potentially leaky C function when the -perl interpreter is embedded in another application. You can force perl -to always use C by compiling with -C<-Accflags="-DPERL_USE_SAFE_PUTENV">, see section L. You can force an embedded perl -to use direct manipulation by setting C after -the C call. - =head3 External glob Before File::Glob entered core in 5.6.0 globbing was implemented by shelling -- cgit v1.2.1