From: Leon Brocard Date: Wed, 26 Mar 2008 10:53:43 +0000 (+0000) Subject: Re: [PATCH] perlhack.pod update walkthrough X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?a=commitdiff_plain;h=9df8f87f35bbd21fa58b4d70ffdb1ad756f24463;p=p5sagit%2Fp5-mst-13.2.git Re: [PATCH] perlhack.pod update walkthrough From: "Leon Brocard" Message-ID: p4raw-id: //depot/perl@33570 --- diff --git a/pod/perlhack.pod b/pod/perlhack.pod index d76261d..cf38f03 100644 --- a/pod/perlhack.pod +++ b/pod/perlhack.pod @@ -760,8 +760,11 @@ This is very high-level code, enough to fit on a single screen, and it resembles the code found in L; most of the real action takes place in F +F is generated by L from F at +make time, so you should make perl to follow this along. + First, F allocates some memory and constructs a Perl -interpreter: +interpreter, along these lines: 1 PERL_SYS_INIT3(&argc,&argv,&env); 2 @@ -790,16 +793,19 @@ later: C is either your system's C, or Perl's own C as defined in F if you selected that option at configure time. -Next, in line 7, we construct the interpreter; this sets up all the -special variables that Perl needs, the stacks, and so on. +Next, in line 7, we construct the interpreter using perl_construct, +also in F; this sets up all the special variables that Perl +needs, the stacks, and so on. Now we pass Perl the command line options, and tell it to go: exitstatus = perl_parse(my_perl, xs_init, argc, argv, (char **)NULL); - if (!exitstatus) { - exitstatus = perl_run(my_perl); - } + if (!exitstatus) + perl_run(my_perl); + + exitstatus = perl_destruct(my_perl); + perl_free(my_perl); C is actually a wrapper around C, as defined in F, which processes the command line options, sets up any @@ -3112,10 +3118,10 @@ then finally report any memory problems. =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. +and illegal memory accesses. As of version 3.3.0, Valgrind only +supports Linux on x86, x86-64 and PowerPC. 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. Valgrind also provides a cachegrind tool, invoked on perl as: