X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?a=blobdiff_plain;f=pod%2Fperlhack.pod;h=2d05fc3841a07f6a1634a7042ea88e0cb8ade5ff;hb=c83084d1250c5e3fe3236f495fb04a079ccb34d8;hp=6e5d5f5a4c7cf3767b5da89126f7c99e34a54ab5;hpb=3fd28c4e2d08a0b6b620046df4e9eb38af3a7913;p=p5sagit%2Fp5-mst-13.2.git diff --git a/pod/perlhack.pod b/pod/perlhack.pod index 6e5d5f5..2d05fc3 100644 --- a/pod/perlhack.pod +++ b/pod/perlhack.pod @@ -1216,6 +1216,14 @@ important ones are explained in L as well. Pay special attention to L for information on the C<[pad]THX_?> macros. +=head2 The .i Targets + +You can expand the macros in a F file by saying + + make foo.i + +which will expand the macros using cpp. Don't be scared by the results. + =head2 Poking at Perl To really poke around with Perl, you'll probably want to build Perl for @@ -1309,8 +1317,11 @@ blessing when stepping through miles of source code. =item print Execute the given C code and print its results. B: Perl makes -heavy use of macros, and F is not aware of macros. You'll have to -substitute them yourself. So, for instance, you can't say +heavy use of macros, and F does not necessarily support macros +(see later L). You'll have to substitute them +yourself, or to invoke cpp on the source code files +(see L) +So, for instance, you can't say print SvPV_nolen(sv) @@ -1318,11 +1329,19 @@ but you have to say print Perl_sv_2pv_nolen(sv) +=back + You may find it helpful to have a "macro dictionary", which you can produce by saying C. Even then, F won't -recursively apply the macros for you. +recursively apply those macros for you. -=back +=head2 gdb macro support + +Recent versions of F have fairly good macro support, but +in order to use it you'll need to compile perl with macro definitions +included in the debugging information. Using F version 3.1, this +means configuring with C<-Doptimize=-g3>. Other compilers might use a +different switch (if they support debugging macros at all). =head2 Dumping Perl Data Structures @@ -1719,6 +1738,18 @@ modules hanging around in here that need to be moved out into F. Testing features of how perl actually runs, including exit codes and handling of PERL* environment variables. +=item F + +Tests for the core support of Unicode. + +=item F + +Windows-specific tests. + +=item F + +A test suite for the s2p converter. + =back The core uses the same testing style as the rest of Perl, a simple @@ -1786,6 +1817,12 @@ Run all the tests through the B::Deparse. Not all tests will succeed. Run F on F, F, F, F, F, F, and F tests. +=item test.valgrind check.valgrind utest.valgrind ucheck.valgrind + +(Only in Linux) Run all the tests using the memory leak + naughty +memory access tool "valgrind". The log files will be named +F. + =item test.third check.third utest.third ucheck.third (Only in Tru64) Run all the tests using the memory leak + naughty @@ -1795,7 +1832,7 @@ F. =item test.torture torturetest Run all the usual tests and some extra tests. As of Perl 5.8.0 the -only extra tests are Abigail's JAPHs, t/japh/abigail.t. +only extra tests are Abigail's JAPHs, F. You can also run the torture test with F by giving C<-torture> argument to F. @@ -1804,6 +1841,59 @@ C<-torture> argument to F. Run all the tests with -Mutf8. Not all tests will succeed. +=item test_harness + +Run the test suite with the F controlling program, instead of +F. F is more sophisticated, and uses the +L module, thus using this test target supposes that perl +mostly works. The main advantage for our purposes is that it prints a +detailed summary of failed tests at the end. Also, unlike F, it +doesn't redirect stderr to stdout. + +=back + +=head2 Running tests by hand + +You can run part of the test suite by hand by using one the following +commands from the F directory : + + ./perl -I../lib TEST list-of-.t-files + +or + + ./perl -I../lib harness list-of-.t-files + +(if you don't specify test scripts, the whole test suite will be run.) + +You can run an individual test by a command similar to + + ./perl -I../lib patho/to/foo.t + +except that the harnesses set up some environment variables that may +affect the execution of the test : + +=over 4 + +=item PERL_CORE=1 + +indicates that we're running this test part of the perl core test suite. +This is useful for modules that have a dual life on CPAN. + +=item PERL_DESTRUCT_LEVEL=2 + +is set to 2 if it isn't set already (see L) + +=item PERL + +(used only by F) if set, overrides the path to the perl executable +that should be used to run the tests (the default being F<./perl>). + +=item PERL_SKIP_TTY_TEST + +if set, tells to skip the tests that need a terminal. It's actually set +automatically by the Makefile, but can also be forced artificially by +running 'make test_notty'. + =back =head1 EXTERNAL TOOLS FOR DEBUGGING PERL @@ -1814,6 +1904,38 @@ some common testing and debugging tools with Perl. This is meant as a guide to interfacing these tools with Perl, not as any kind of guide to the use of the tools themselves. +B: Running under memory debuggers such as Purify, valgrind, or +Third Degree greatly slows down the execution: seconds become minutes, +minutes become hours. For example as of Perl 5.8.1, the +ext/Encode/t/Unicode.t takes extraordinarily long to complete under +e.g. Purify, Third Degree, and valgrind. Under valgrind it takes more +than six hours, even on a snappy computer-- the said test must be +doing something that is quite unfriendly for memory debuggers. If you +don't feel like waiting, that you can simply kill away the perl +process. + +B: To minimize the number of memory leak false alarms (see +L for more information), you have to have +environment variable PERL_DESTRUCT_LEVEL set to 2. The F +and harness scripts do that automatically. But if you are running +some of the tests manually-- for csh-like shells: + + setenv PERL_DESTRUCT_LEVEL 2 + +and for Bourne-type shells: + + PERL_DESTRUCT_LEVEL=2 + export PERL_DESTRUCT_LEVEL + +or in UNIXy environments you can also use the C command: + + env PERL_DESTRUCT_LEVEL=2 valgrind ./perl -Ilib ... + +B: There are known memory leaks when there are compile-time +errors within eval or require, seeing C in the call stack +is a good sign of these. Fixing these leaks is non-trivial, +unfortunately, but they must be fixed eventually. + =head2 Rational Software's Purify Purify is a commercial tool that is helpful in identifying @@ -1822,11 +1944,6 @@ badness. Perl must be compiled in a specific way for optimal testing with Purify. Purify is available under Windows NT, Solaris, HP-UX, SGI, and Siemens Unix. -The only currently known leaks happen when there are -compile-time errors within eval or require. (Fixing these -is non-trivial, unfortunately, but they must be fixed -eventually.) - =head2 Purify on Unix On Unix, Purify creates a new Perl binary. To get the most @@ -1875,17 +1992,6 @@ which creates a binary named 'pureperl' that has been Purify'ed. This binary is used in place of the standard 'perl' binary when you want to debug Perl memory problems. -To minimize the number of memory leak false alarms -(see L), set environment variable -PERL_DESTRUCT_LEVEL to 2. - - setenv PERL_DESTRUCT_LEVEL 2 - -In Bourne-type shells: - - PERL_DESTRUCT_LEVEL=2 - export PERL_DESTRUCT_LEVEL - As an example, to show any memory leaks produced during the standard Perl testset you would create and run the Purify'ed perl as: @@ -1968,13 +2074,22 @@ standard Perl testset you would create and run Purify as: which would instrument Perl in memory, run Perl on test.pl, then finally report any memory problems. -B: as of Perl 5.8.0, the ext/Encode/t/Unicode.t takes -extraordinarily long (hours?) to complete under Purify. It has been -theorized that it would eventually finish, but nobody has so far been -patient enough :-) (This same extreme slowdown has been seen also with -the Third Degree tool, so the said test must be doing something that -is quite unfriendly for memory debuggers.) It is suggested that you -simply kill away that testing process. +=head2 valgrind + +The excellent valgrind tool can be used to find out both memory leaks +and illegal memory accesses. As of August 2003 it unfortunately works +only on x86 (ELF) Linux. The special "test.valgrind" target can be used +to run the tests under valgrind. Found errors and memory leaks are +logged in files named F. + +As system libraries (most notably glibc) are also triggering errors, +valgrind allows to suppress such errors using suppression files. The +default suppression file that comes with valgrind already catches a lot +of them. Some additional suppressions are defined in F. + +To get valgrind and for more information see + + http://developer.kde.org/~sewardj/ =head2 Compaq's/Digital's/HP's Third Degree @@ -2007,12 +2122,12 @@ aren't. See L for more information. =head2 PERL_DESTRUCT_LEVEL -If you want to run any of the tests yourself manually using the -pureperl or perl.third executables, please note that by default -perl B explicitly cleanup all the memory it has allocated -(such as global memory arenas) but instead lets the exit() of -the whole program "take care" of such allocations, also known -as "global destruction of objects". +If you want to run any of the tests yourself manually using e.g. +valgrind, or the pureperl or perl.third executables, please note that +by default perl B explicitly cleanup all the memory it has +allocated (such as global memory arenas) but instead lets the exit() +of the whole program "take care" of such allocations, also known as +"global destruction of objects". There is a way to tell perl to do complete cleanup: set the environment variable PERL_DESTRUCT_LEVEL to a non-zero value.