-
Notifications
You must be signed in to change notification settings - Fork 560
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bug in perldiag #175
Comments
From jdporter@sprint.netperldiag appears to have a tiny -- but important error. Bad free() ignored But, AFAICT, that should be 0 (zero), not 1. if (bad_free_warn == -1) { And indeed, setting PERL_BADFREE to 0 *DOES* silence the warning, The documentation goes on to say: This message can be quite often seen with DB_File on systems with But I experienced it (on Solaris 2.6) when attempting to set an Perl Info
|
From @rspierfixing old bugs.... http://bugs.perl.org/admin/perlbug.cgi?req=tid&tid=19990709.002 for rationale. -R [against perl-current] Inline Patch--- perldiag.pod.1 Thu Jul 27 09:43:43 2000
+++ perldiag.pod Thu Jul 27 09:47:46 2000
@@ -261,9 +261,9 @@
(S malloc) An internal routine called free() on something that had never
been malloc()ed in the first place. Mandatory, but can be disabled by
-setting environment variable C<PERL_BADFREE> to 1.
+setting environment variable C<PERL_BADFREE> to 0.
-This message can be quite often seen with DB_File on systems with "hard"
+This message can be seen quite often with DB_File on systems with "hard"
dynamic linking, like C<AIX> and C<OS/2>. It is a bug of C<Berkeley DB>
which is left unnoticed if C<DB> uses I<forgiving> system malloc(). |
From @jhiOn Thu, Jul 27, 2000 at 09:49:35AM -0400, Robert Spier wrote:
Thanks, applied. |
From The RT System itselfmarked [on hold] pending patch approval |
From The RT System itselfclosed: patch accepted |
Migrated from rt.perl.org#980 (status was 'resolved')
Searchable as RT980$
The text was updated successfully, but these errors were encountered: