Mailing-List: contact modperl-help@perl.apache.org; run by ezmlm
Precedence: bulk
Received-SPF: neutral (herse.apache.org: 207.114.11.197 is neither permitted
 nor denied by domain of perrin@elem.com)
Subject: Re: Subroutine xxx redefined
From: Perrin Harkins <perrin@elem.com>
To: Bart van Kuik <b.van.kuik@sron.nl>
Cc: modperl@perl.apache.org
In-Reply-To: <453DC40D.8050404@sron.nl>
References: <4539009C.6090009@sron.nl>
	 <73ddeb6c0610201131v20a65883l2e7c11ecd6543124@mail.gmail.com>
	 <453C979F.7080809@sron.nl> <1161630920.5412.49.camel@localhost.localdomain>
	 <453DC40D.8050404@sron.nl>
Content-Type: text/plain
Date: Tue, 24 Oct 2006 17:15:56 -0400
Message-Id: <1161724556.17044.59.camel@localhost.localdomain>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit

On Tue, 2006-10-24 at 09:43 +0200, Bart van Kuik wrote:
> The before-mentioned piece of script gives the following warning:
> Subroutine testsub redefined at /home/bartvk/public_html/tscu/test.pl 
> line 7.

The same every time?  That's very strange.  I'd start adding some debug
statements to Apache::PerlRun to make sure it really is handling this
script.  In particular, I'd put some warnings in the flush_namespace()
sub to see if it is trying to clear out that sub or not.

One possible explanation for this behavior is that something which did
not warn in older versions of perl (when it was more likely to be
running mod_perl 1 and Apache::PerlRun) now does.  In that case, it
should be possible to patch PerlRun to suppress the warning.  But first,
make sure PerlRun is really running your script and clearing the symbol
table afterward.

> Clicking on the module name gives a screen with a list of functions; I 
> don't really see how to get more information on PerlRun.

Apologies, it shows a lot more detail for Apache::Registry but not for
PerlRun.  You can browse the symbol table of loaded packages though, I
believe, which would include the package generated for your script.

- Perrin