| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
|
| |
(For core modules, or where the dual life module on CPAN has a Makefile.PL that
is not the same. AUTHOR is only used for the ppm target, which the core doesn't
need.)
|
| |
|
| |
|
| |
|
|
|
|
|
| |
Remove some orphaned trailing quotes from TODO message that are no longer
conditional code.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
SKIPs.
|
| |
|
| |
|
| |
|
|
|
|
|
| |
(Which was actually a dangling cross reference, as what it pointed to in
perlfunc had already been deleted.)
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
pod/perlthrtut.pod is the same material reworked for ithreads.
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
This trivial patch lets C89-ish compilers compile Socket.c again.
Signed-off-by: H.Merijn Brand <h.m.brand@xs4all.nl>
|
| |
|
|\ |
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This happens on boxes which otherwise work Just Fine and whose resolvers
work Just Fine if they don't have /etc/hosts. This patch fixes the test
file by making it skip if localhost can't be resolved and /etc/hosts
doesn't exist.
Message-ID: <20090330205715.GA29690@bytemark.barnyard.co.uk>
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Message-ID: <20081026231720.34258457@r2d2>
Patch description from the original email :
I tried to make tests pass on a perl built with -DPERL_POISON,
as some tests were dying with segfaults. They all originated
from the same source: clear_yystack() after a compile error. [...]
As far as I can see, after croaking the newly
created CV is destroyed and its pad is undef'd. [...]
This will SvREFCNT_dec PL_comppad and set PL_comppad to NULL.
However, later, in clear_yystack(), when the ops are freed, the
old PL_comppad is restored by PAD_RESTORE_LOCAL, as a reference
is still in ps->comppad. But now the pad AV is already dead.
Normally (i.e. without PERL_POISON), the dead AV will have
AvARRAY(av) set to NULL by av_undef(). So PAD_RESTORE_LOCAL will
actually set PL_curpad to NULL, and thus pad_free() will not
attempt to do anything.
But with PERL_POISON, the storage for AvARRAY(av) (i.e. sv_u)
will be reused for chaining the free SV heads in the arena
(as opposed to SvANY(sv) in case of !PERL_POISON). This means
that PAD_RESTORE_LOCAL will find AvARRAY(av) non-NULL and will
set PL_curpad to that value, finally causing the segfault in
pad_free().
While I think I understand what's going on, I don't have the
slightest clue how to properly fix this. Given that it's not
a problem only under PERL_POISON, but always (as dead SV heads
are being used), I think it should ultimately be fixed.
The only thing I can offer right now is a patch to make it
work with PERL_POISON as good (or as bad) as without by
making PAD_RESTORE_LOCAL explicitly check if the pad passed
in is already dead and refusing to use it if it is.
|
|/
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Patch and description by Rainer Weikusat, forwarded from
http://bugs.debian.org/502297 :
The h2xs program scans C headers for 'constants' either defined
as preprocessor macros or via enum and builds a sorted list of names
containing the macros and enum values found in this way. This list
is then passed to ExtUtils::Constant::WriteConstants, which generates
the corresponding const-c.inc and const-xs.inc files when perl Makefile.PL
is executed. By default, ie when just processing a constant name, this
function assumes that the name refers to a preprocessor macro and
the generated C-code in const-c.inc contains conditional compilation
directives to either return the macro value or Perl_constant_NOTDEF,
depending on the defined'ness of the macro. This causes constants
defined as enumeration values to never be available to module users,
because they are not visible to the preprocessor.
Instead of passing just a name to the WriteConstants-routine, a
hashref (members documented in ExtUtils::Constant::Base(3perl))
can be used to specify more details regarding what code
should be generated for a particular constant. For an enumeration
value, a hashref constructed as
{ name => <name of the constant>, macro => 1 }
could be used to get rid of the inappropriate preprocessor
directives.
( Another version of the same fix was also submitted by Daniel Burr in
http://bugs.debian.org/320286 )
|
|
|
|
|
|
|
| |
I read through each my patches again and came across a typo,
a slight incorrectness, and a repeated word. Sorry.
Signed-off-by: Michael Witten <mfwitten@gmail.com>
|
|
|
|
| |
Yeah, well, I wrote some new stuff.
|
|
|
|
| |
Signed-off-by: Michael Witten <mfwitten@gmail.com>
|
|
|
|
| |
Signed-off-by: Michael Witten <mfwitten@gmail.com>
|
|
|
|
| |
Signed-off-by: Michael Witten <mfwitten@gmail.com>
|
|
|
|
| |
Signed-off-by: Michael Witten <mfwitten@gmail.com>
|
|
|
|
| |
Signed-off-by: Michael Witten <mfwitten@gmail.com>
|
|
|
|
| |
Signed-off-by: Michael Witten <mfwitten@gmail.com>
|
|
|
|
| |
Signed-off-by: Michael Witten <mfwitten@gmail.com>
|
|
|
|
| |
Signed-off-by: Michael Witten <mfwitten@gmail.com>
|
|
|
|
| |
Signed-off-by: Michael Witten <mfwitten@gmail.com>
|
|
|
|
| |
Signed-off-by: Michael Witten <mfwitten@gmail.com>
|
|
|
|
| |
Signed-off-by: Michael Witten <mfwitten@gmail.com>
|
|
|
|
| |
Signed-off-by: Michael Witten <mfwitten@gmail.com>
|
|
|
|
| |
Signed-off-by: Michael Witten <mfwitten@gmail.com>
|
|
|
|
|
|
|
|
|
|
|
|
| |
As seen in <http://bugs.debian.org/522673>, since 4.2.0 or so
gcc's search path has a new "include-fixed" directory,
which currently contains <syslimits.h> and a few other headers.
Converting <syslimits.h> therefore fails unless h2ph knows about the new
directory too.
See http://gcc.gnu.org/ml/gcc-patches/2007-02/msg02038.html for some
background to the gcc change.
|
|
|
|
|
|
|
| |
Based on a patch by James Mastros :
Subject: Deprecating $[
Message-ID: <abc933c50904020726x31776ab5m192036429af16f03@mail.gmail.com>
|