Kjetil Kjernsmo wrote:
We have seen a problem with server errors when getting malformed
cookies. The problem has been seen before, we found from googling [1],
but it is not clear how we should address this. We are not quite
positive about the source of the malformed cookies, (it may have been
Philip G. Gollucci wrote:
You are correct in what it does; however, its not an issue as far as I can
see. The reason being is that the last arg of connect is the \%attrs hash
ref. Its replacing the password with *'s and then showing all SCALAR (aka
simple to the lazy programer) parameters :)
Philip, I think I've spotted another small Apache/DBI issue that I thought I
would run by you.
In the 'connect' function inside the DBI.pm module (as opposed to the
Apache/DBI.pm) there are somes lines about 12 lines down from the start of
the 'connect' function that reads as follows
Joshua Hoblitt wrote:
On Thu, Jun 30, 2005 at 11:25:26AM -0400, Philip M. Gollucci wrote:
Mark A. Downing wrote:
On Thu, 30 Jun 2005, Philip M. Gollucci wrote:
Thanks for this Mark. (Un)fortunately you've been beat to it and
there are few more changes to
get all of it
Douglas Riordan wrote:
On 6/27/05, Philip M. Gollucci [EMAIL PROTECTED] wrote:
Douglas Riordan wrote:
from Apache2::Const's perldoc
use Apache2::Const qw(OK);
compiles imports the OK constant.
use Apache2::Const -compile = qw(OK);
only compiles the OK constant in which case i would have
Stas Bekman wrote:
I discovered what was causing the problem. Even though I had used the
following in the startup.pl file
use Apache2::Const -compile = ':common';
the Apache modules were segfaulting on the straight 'OK' constant
declarations in them.
Vincent, what do you mean by
Vincent Moneymaker wrote:
I am running Apache 2.0.52 on a solaris 8 box with mod_perl-2.0.0-RC5. I
previously had problems using Apache::Reload with mod_perl 1.99_19 version
back in December and gave up trying to find a fix. I thought I would try
again with the RC5 version but after having
Vincent Moneymaker wrote:
Here is the output from the backtrace (hope I did it correctly)
Program received signal SIGSEGV, Segmentation fault.
0xdeb3618f in Perl_gv_efullname3 () from
/opt/prod/apache/modules/mod_perl.so
(gdb) bt
#6 0xdeb9293f in Perl_pp_require () from
/opt/prod/apache
Vincent Moneymaker wrote
Vincent Moneymaker wrote:
Vincent Moneymaker wrote:
Here is the output from the backtrace (hope I did it correctly)
Program received signal SIGSEGV, Segmentation fault.
0xdeb3618f in Perl_gv_efullname3 () from
/opt/prod/apache/modules/mod_perl.so
(gdb) bt
#6 0xdeb9293f
Vince Moneymaker wrote:
Okay, all of the tests are being passed. I have added the contents of my
startup.pl file to the modperl_startup.pl file and no segfaults are
occurring including even when I change the Handler.pm file as the tests
are being run on it. I have also added some items to the
I am running Apache 2.0.52 on a solaris 8 box with mod_perl-2.0.0-RC5. I
previously had problems using Apache::Reload with mod_perl 1.99_19 version
back in December and gave up trying to find a fix. I thought I would try
again with the RC5 version but after having upgraded from mod_perl
Thomas den Braber wrote:
The main module reloads without problems, most of the modules that are used
from the main module (with use) do not reload automatically.
That's the problem I am seeing
Philippe M. Chiasson wrote:
Possibly a problem with clear_stash()
[...]
so both modules are located in the same directory, right? Can you reduce
those module to the very minimum while one still reloads and the other
doesn't and post them here, and I'll try to reproduce it here. Also
please
Stas Bekman wrote:
But you also indicated that all versions before 1.99_17 did work w/o the
package declaration, so that would be mean a behavior change.
First the results. I applied Philippe's patch, but no Reload messages
showed up in the error log when changes were made to the Menus.pm
I am running Apache 2.0.52 on a solaris 8 box with mod_perl 1.99_12. Over
the weekend I tried to upgrade to the 1.99_19 version of mod_perl. With
mod_perl 1.99_12 all of the requisite modules reloaded properly when their
contents changed. However, with the 1.99_19 version some modules are not
15 matches
Mail list logo