On Tue, May 29, 2012 at 12:07 PM, Doug Hunt wrote:
> Hi mod_perl list!
>
> I've been using Apache and mod_perl for a long time on our web site, but I'm
> having troubles getting it to compile under the most recent Apache, mod_perl
> and perl.
>
> I'm working under CentOS 6.2 on an x86_64 system.
>
On Tue, Feb 8, 2011 at 16:26, Max Pinton wrote:
> On Feb 8, 2011, at 7:36 AM, Perrin Harkins wrote:
>> That doesn't explain all of your errors though. I'm guessing that
>> you're opening a connection during startup and forking with it. You
>> need to find that. Look for things that might open a
>>> On Wed, Jun 30, 2010 at 02:49, Tim Bunce wrote:
>>> > I suggest the code shift items off the main array, like perl does,
>>> > but also push those items onto a new temp array.
Find attached a patch that does the above (perhaps naively), passes a
make test and fixes the reported problems for m
On Wed, Jun 30, 2010 at 16:37, Tim Bunce wrote:
> On Wed, Jun 30, 2010 at 09:24:42AM -0600, Alex Hunsaker wrote:
>> On Wed, Jun 30, 2010 at 02:49, Tim Bunce wrote:
>> > I suggest the code shift items off the main array, like perl does,
>> > but also push those items
On Wed, Jun 30, 2010 at 02:49, Tim Bunce wrote:
> On Tue, Jun 29, 2010 at 09:50:00PM -0700, Fred Moyer wrote:
>> I think getting rid of the segfault is a good thing. But if the main
>> problem is issues with NYTProf, then it seems like this change won't
>> solve the core problem of autogenerated
Hi!
perl: 5.10.1, 5.12.1 (i686-linux, x86_64-linux)
mod_perl: 2.0.4
Basically if you have end blocks that modify/add END blocks things
might go crazy.
A simple test case for this is:
package test:
END { eval "END { }" for 1..10 }
gives:
Not a CODE reference.
END failed--call queue aborted.
if
This Patch fixes annoying log messages (notably with postgresql, but
others may apply) because Apache::DBI fails to disconnect properly at
exit time.
(it stops the buggers below from filling my logs...)
LOG: unexpected EOF on client connection
LOG: could not receive data from client: Connection
