Re: Bugs 5.6.0 modperl use?
> Well, that turned out to be a challenging request! > Here's a module that always segfaults, if you run with > httpd -X -Dperldb -Dperlsi Sorry, I forgot to mention... the segfault only occurs if you _don't_ have Net::DNS installed. -- Jeremy Howard [EMAIL PROTECTED]
Re: Bugs 5.6.0 modperl use?
> > > [Wed May 24 19:58:28 2000] [error] PerlRun: `Bizarre copy of HASH in aassign
> > > at /usr5/perl/lib/5.6.0/Carp/Heavy.pm line 79.
> > > ...
> > Do the following:
> >
> > In Carp::Heavy, change 'DB' to 'DB_tmp':
> > Line 39: while (do { { package DB_tmp; @a = caller($i++) } } ) {
> > Line 79: @a = @{DB_tmp::args}; # must get local copy of args
> >
> > In CGI::Carp, change Line 257:
> > FROM: my $message = shift;
> > TO: my ($message) = @_;
> > ...
> do you have small test case to reproduce this bug?
Well, that turned out to be a challenging request! Here's a module that
always segfaults, if you run with
httpd -X -Dperldb -Dperlsi
#!/usr/bin/perl -w
package MailApp::temp;
use CGI::Carp ;
use Apache ();
if (Apache->server->dir_config('InDB')) {
1;
}
use Email::Valid ();
$a = Email::Valid->mx(1);
1;
And here's my perl.conf (which defines the perldb and perlsi symbols):
PerlSetVar InDB 1
PerlFreshRestart On
PerlRequire conf/startup.pl
PerlModule Apache::StatINC
PerlInitHandler Apache::StatINC
PerlSetVar StatINCDebug On
PerlTaintCheck On
PerlFixupHandler Apache::DB
SetHandler perl-script
PerlHandler MailApp::temp
Order deny,allow
Allow from all
Note that there's no 'use Apache::DB'--httpd segfaults with or without
it... So it doesn't seem to be a debugger bug.
If I remove _any_ of the lines from the test module, I don't get the
error. That's why it's so hard to debug and replicate.
--
Jeremy Howard
[EMAIL PROTECTED]
Re: Bugs 5.6.0 modperl use?
On Thu, Jun 01, 2000 at 12:00:45PM -0700, Doug MacEachern wrote: > On Fri, 26 May 2000, Michael hall wrote: > > > On Fri, May 26, 2000 at 01:36:33AM -0400, Jeff Stuart wrote: > > > > > Ok, follow up question if I may. :) Are any of you using it with DBI and > > > DBD::mysql? I see on the Mason list that people are using it with > > > HTML::Mason so that module is safe. :) Looks like I'm gonna have to pull > > > out that old Linux box and do a test on it. :) > > > > Using DBI, DBD:mysql, and perl 5.60 (compiled with -DUseThreads) here. Doug > > was kind enough to post a couple of patches for DBI and DBD:mysql to get > > them to compile (when using -DUseThreads). I wouldn't call it a production > > server though since its very low volume, but I haven't had any problems > > with it. > > did you forward those patches along to the authors? Yes, and also posted them on the 'dbi-users' list. Other than a few requests for them from others (which I sent them :-) I haven't had any response from either Tim or Joachim (sp?). Just installed a new Mysql-modules the other day, no changes I could see so I just applied your patch and compiled it otherwise it failed with the same old stuff. Tim posted a message awhile ago that there would be a new version of DBI coming out soon, hopefully it'll incorporate some fixes. -- Do I have to pee whenever I see this sign ? WET FLOOR... Mike Hall, Unix Admin - Rock Island Communications <[EMAIL PROTECTED]> System Admin - riverside.org<[EMAIL PROTECTED]>
Re: Bugs 5.6.0 modperl use?
On Fri, 26 May 2000, Michael hall wrote: > On Fri, May 26, 2000 at 01:36:33AM -0400, Jeff Stuart wrote: > > > Ok, follow up question if I may. :) Are any of you using it with DBI and > > DBD::mysql? I see on the Mason list that people are using it with > > HTML::Mason so that module is safe. :) Looks like I'm gonna have to pull > > out that old Linux box and do a test on it. :) > > Using DBI, DBD:mysql, and perl 5.60 (compiled with -DUseThreads) here. Doug > was kind enough to post a couple of patches for DBI and DBD:mysql to get > them to compile (when using -DUseThreads). I wouldn't call it a production > server though since its very low volume, but I haven't had any problems > with it. did you forward those patches along to the authors?
Re: Bugs 5.6.0 modperl use?
On Thu, 25 May 2000, Jeremy Howard wrote:
> > CGI::Carp preloaded.
> > DBI preloaded.
> >
> > [Wed May 24 19:58:28 2000] [error] PerlRun: `Bizarre copy of HASH in aassign
> > at /usr5/perl/lib/5.6.0/Carp/Heavy.pm line 79.
> >
> > ...
> > Anyone else seen these?
>
> Oh yes, I've been battling that tonight...
>
> Do the following:
>
> In Carp::Heavy, change 'DB' to 'DB_tmp':
> Line 39: while (do { { package DB_tmp; @a = caller($i++) } } ) {
> Line 79: @a = @{DB_tmp::args}; # must get local copy of args
>
> In CGI::Carp, change Line 257:
> FROM: my $message = shift;
> TO: my ($message) = @_;
>
> Yes, this really does matter--I carefully reproduced a problem that only
> occured when 'shift' was used!
do you have small test case to reproduce this bug? i wasn't able to, but
poked around a bit and see:
#Carp.pm:
sub longmess {
{ local $@; require Carp::Heavy; } # XXX fix require to not clear $@?
goto &longmess_heavy;
}
and perl.c:call_sv():
PL_eval_root = PL_op; /* Only needed so that goto works right.*/
which leads me to think goto() + call_sv() (which is how mod_perl
invokes handlers) can lead to trouble, we just need to figure out exactly
what is tripping it up. it's not clear from the module changes you made
to bandaid the bug, i'd like to be able to reproduce this and step in with
gdb. i have a feeling it's something to do with AUTOLOAD+eval "" changing
PL_eval_root, but i can only guess at this point.
RE: Bugs 5.6.0 modperl use?
Well, I haven't used it for long (obviously, I suppose...;), but our digitalmass.com domain is currently running a 5.6.0/1.24/1.3.12 combination, and seems to be holding up well. We *do* have a periodic problem with a child process going haywire and twisting itself into a tight 'sbrk' loop, but we've seen this on our 5.00503/1.23 setups too, it's just something odd that we haven't been able to trace down as of yet. I've been using a simple monitoring script to watch for these and kill them off when needed, and I get 2 or three a day. So I guess my answer is, "seems ok to us..."! On Thu, 25 May 2000, Jeff Stuart wrote: > That's a GOOD question. Is there anyone at the moment using perl 5.6.0 in > production? Is it ready for production yet? > > -- > Jeff (FurBall) > WebOverdrive Newbie Tech Board > http://www.topniche.com/tech/ > [EMAIL PROTECTED] > =-=-=-=-=-=-=-=-=-=- My God! What have I done? -=-=-=-=-=-=-=-=-=-= Steve Reppucci [EMAIL PROTECTED] | Logical Choice Software http://logsoft.com/ | 508/958-0183 Be Open |
RE: Bugs 5.6.0 modperl use?
On Fri, 26 May 2000, Jeff Stuart wrote: > Ok, follow up question if I may. :) Are any of you using it with DBI and > DBD::mysql? I see on the Mason list that people are using it with > HTML::Mason so that module is safe. :) Looks like I'm gonna have to pull Except that if you use the html error mode your traces will be hosed by a bug in the caller function. -dave (waiting for 5.6.1) /*== www.urth.org We await the New Sun ==*/
Re: Bugs 5.6.0 modperl use?
On Fri, May 26, 2000 at 01:36:33AM -0400, Jeff Stuart wrote: > Ok, follow up question if I may. :) Are any of you using it with DBI and > DBD::mysql? I see on the Mason list that people are using it with > HTML::Mason so that module is safe. :) Looks like I'm gonna have to pull > out that old Linux box and do a test on it. :) Using DBI, DBD:mysql, and perl 5.60 (compiled with -DUseThreads) here. Doug was kind enough to post a couple of patches for DBI and DBD:mysql to get them to compile (when using -DUseThreads). I wouldn't call it a production server though since its very low volume, but I haven't had any problems with it. You can search the archives for 'Subject: Re: mod_perl 2.x/perl 5.6.x ?' to find the patches or email me and I'll send them. -- He was so crooked you could use him to pull corks with. Mike Hall, Unix Admin - Rock Island Communications <[EMAIL PROTECTED]> System Admin - riverside.org<[EMAIL PROTECTED]>
RE: Bugs 5.6.0 modperl use?
We are running 5.6 on 2 production servers with mod_perl 1.23 and 1.24, Apache 1.3.12, Apache::DBI, DBD::Sybase (to MSSQL), and DBD::mysql. One box is Linux. The other is Solaris 2.7. So far no issues other than "depreciated" notices on some modules, and our own programming errors. Serving ~6M dynamic page views per month between the two boxes. They both seem quite stable now that our own bugs are ironed out... ;-) -Original Message- From: Jeff Stuart [mailto:[EMAIL PROTECTED]] Sent: Friday, May 26, 2000 12:37 AM To: Jim Winstead; Modperl Mailing List Cc: [EMAIL PROTECTED] Subject: RE: Bugs 5.6.0 modperl use? Ok, follow up question if I may. :) Are any of you using it with DBI and DBD::mysql? I see on the Mason list that people are using it with HTML::Mason so that module is safe. :) Looks like I'm gonna have to pull out that old Linux box and do a test on it. :) -- Jeff (FurBall) WebOverdrive Newbie Tech Board http://www.topniche.com/tech/ [EMAIL PROTECTED] -Original Message- From: Jim Winstead [mailto:[EMAIL PROTECTED]] Sent: Thursday, May 25, 2000 10:46 PM To: Modperl Mailing List Subject: Re: Bugs 5.6.0 modperl use? On May 25, Jeff Stuart wrote: > That's a GOOD question. Is there anyone at the moment using perl 5.6.0 in > production? Is it ready for production yet? We have one site in production with it, and a number of others going into production soon. We've been using is exclusively in our development environment for all new development since shortly after 5.6.0 came out. It has been rock-solid for us. (The basic setup is Apache 1.3.12, mod_perl 1.24, perl 5.6.0, and FreeBSD 3.4.) Jim
RE: Bugs 5.6.0 modperl use?
Ok, follow up question if I may. :) Are any of you using it with DBI and DBD::mysql? I see on the Mason list that people are using it with HTML::Mason so that module is safe. :) Looks like I'm gonna have to pull out that old Linux box and do a test on it. :) -- Jeff (FurBall) WebOverdrive Newbie Tech Board http://www.topniche.com/tech/ [EMAIL PROTECTED] -Original Message- From: Jim Winstead [mailto:[EMAIL PROTECTED]] Sent: Thursday, May 25, 2000 10:46 PM To: Modperl Mailing List Subject: Re: Bugs 5.6.0 modperl use? On May 25, Jeff Stuart wrote: > That's a GOOD question. Is there anyone at the moment using perl 5.6.0 in > production? Is it ready for production yet? We have one site in production with it, and a number of others going into production soon. We've been using is exclusively in our development environment for all new development since shortly after 5.6.0 came out. It has been rock-solid for us. (The basic setup is Apache 1.3.12, mod_perl 1.24, perl 5.6.0, and FreeBSD 3.4.) Jim
Re: Bugs 5.6.0 modperl use?
On May 25, Jeff Stuart wrote: > That's a GOOD question. Is there anyone at the moment using perl 5.6.0 in > production? Is it ready for production yet? We have one site in production with it, and a number of others going into production soon. We've been using is exclusively in our development environment for all new development since shortly after 5.6.0 came out. It has been rock-solid for us. (The basic setup is Apache 1.3.12, mod_perl 1.24, perl 5.6.0, and FreeBSD 3.4.) Jim
RE: Bugs 5.6.0 modperl use?
That's a GOOD question. Is there anyone at the moment using perl 5.6.0 in production? Is it ready for production yet? I currently use 5.6.0 (w/ mod_perl 1.24) on all my production servers and 5.6.0 is currently listed as stable so for I don't see any reason as to say it isn't usable for production. Sincerely, Craig Vincent
RE: Bugs 5.6.0 modperl use?
That's a GOOD question. Is there anyone at the moment using perl 5.6.0 in production? Is it ready for production yet? -- Jeff (FurBall) WebOverdrive Newbie Tech Board http://www.topniche.com/tech/ [EMAIL PROTECTED] -Original Message- From: Jeffrey W. Baker [mailto:[EMAIL PROTECTED]] Sent: Thursday, May 25, 2000 3:22 AM To: John M Vinopal Cc: [EMAIL PROTECTED] Subject: Re: Bugs 5.6.0 modperl use? On Wed, 24 May 2000, John M Vinopal wrote: > > Apache 1.3.12 > modperl 1.24 > perl 5.6.0 > > CGI::Carp preloaded. > DBI preloaded. > > [Wed May 24 19:58:28 2000] [error] PerlRun: `Bizarre copy of HASH in aassign > at /usr5/perl/lib/5.6.0/Carp/Heavy.pm line 79. > > Prototype mismatch: sub Apache::ROOT::cgi_2dbin::adtaker::get_username::SQL_INTEGER vs () at /usr5/perl/lib/5.6.0/Exporter.pm line 57. > at /usr5/caps_prod/scripts/adtaker/get_username line 6 > > where SQL_INTEGER is imported via > use DBI qw(SQL_INTEGER); > > Anyone else seen these? Is anyone else using Perl 5.6.0? -jwb
Re: Bugs 5.6.0 modperl use?
Jeffrey W. Baker wrote: > > On Wed, 24 May 2000, John M Vinopal wrote: > > ... > > CGI::Carp preloaded. > > DBI preloaded. > > > > [Wed May 24 19:58:28 2000] [error] PerlRun: `Bizarre copy of HASH in aassign > > at /usr5/perl/lib/5.6.0/Carp/Heavy.pm line 79. > > > > Prototype mismatch: sub >Apache::ROOT::cgi_2dbin::adtaker::get_username::SQL_INTEGER vs () at >/usr5/perl/lib/5.6.0/Exporter.pm line 57. > > at /usr5/caps_prod/scripts/adtaker/get_username line 6 > > > > where SQL_INTEGER is imported via > > use DBI qw(SQL_INTEGER); > > > > Anyone else seen these? > > Is anyone else using Perl 5.6.0? As I mentioned in the message I sent you, Jeff (intended for the whole list, sorry), I installed 5.6.0 yesterday along with some modules I downloaded for a particular project. I immediately started getting the following complaint: Prototype mismatch: sub IO::Handle::blocking ($;$) vs none at /usr/local/lib/perl5/site_perl/5.6.0/LWP/Conn/_Connect.pm line 43. from the following script: #!/usr/bin/perl use LWP::Conn::_Connect; I've been able to at least suppress the complaint by adding a line to _Connect.pm to check the version of IO::Handle (I have 1.21) and not run the hack at the top of the file which is commented as being unnecessary after IO::Handle 1.18. I've sent a message and patch to the author of LWPng (Gisle Aas), which _Connect.pm is part of, asking him to verify whether this fixes or only masks the problem. I'll be glad to make my patch available, but it might be better to wait for Gisle to incorporate it (or something even better :) into LWPng. Tom
Re: Bugs 5.6.0 modperl use?
> CGI::Carp preloaded.
> DBI preloaded.
>
> [Wed May 24 19:58:28 2000] [error] PerlRun: `Bizarre copy of HASH in aassign
> at /usr5/perl/lib/5.6.0/Carp/Heavy.pm line 79.
>
> ...
> Anyone else seen these?
Oh yes, I've been battling that tonight...
Do the following:
In Carp::Heavy, change 'DB' to 'DB_tmp':
Line 39: while (do { { package DB_tmp; @a = caller($i++) } } ) {
Line 79: @a = @{DB_tmp::args}; # must get local copy of args
In CGI::Carp, change Line 257:
FROM: my $message = shift;
TO: my ($message) = @_;
Yes, this really does matter--I carefully reproduced a problem that only
occured when 'shift' was used!
I'll contact the relevant authors tomorrow. I don't know if this is a
Perl 5.6 bug, or a module bug that 5.6 has surfaced.
--
Jeremy Howard
[EMAIL PROTECTED]
Re: Bugs 5.6.0 modperl use?
On Wed, 24 May 2000, John M Vinopal wrote: > > Apache 1.3.12 > modperl 1.24 > perl 5.6.0 > > CGI::Carp preloaded. > DBI preloaded. > > [Wed May 24 19:58:28 2000] [error] PerlRun: `Bizarre copy of HASH in aassign > at /usr5/perl/lib/5.6.0/Carp/Heavy.pm line 79. > > Prototype mismatch: sub Apache::ROOT::cgi_2dbin::adtaker::get_username::SQL_INTEGER >vs () at /usr5/perl/lib/5.6.0/Exporter.pm line 57. > at /usr5/caps_prod/scripts/adtaker/get_username line 6 > > where SQL_INTEGER is imported via > use DBI qw(SQL_INTEGER); > > Anyone else seen these? Is anyone else using Perl 5.6.0? -jwb
Bugs 5.6.0 modperl use?
Apache 1.3.12 modperl 1.24 perl 5.6.0 CGI::Carp preloaded. DBI preloaded. [Wed May 24 19:58:28 2000] [error] PerlRun: `Bizarre copy of HASH in aassign at /usr5/perl/lib/5.6.0/Carp/Heavy.pm line 79. Prototype mismatch: sub Apache::ROOT::cgi_2dbin::adtaker::get_username::SQL_INTEGER vs () at /usr5/perl/lib/5.6.0/Exporter.pm line 57. at /usr5/caps_prod/scripts/adtaker/get_username line 6 where SQL_INTEGER is imported via use DBI qw(SQL_INTEGER); Anyone else seen these? -j
