On Fri, 11 Aug 2000, G.W. Haywood wrote:
What compiler(s)?
gcc -v says:
gcc version egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)
[Cc to Stas as the example in the guide is wrong, and Dave explains
the correct way]
On Mon, Jul 31, 2000 at 03:42:18PM -0400, Dave Moore took time to write:
duh...now that i've had some more coffee...the line:
PerlVersionINC On
must come before the PerlINC statement. PerlINC wont store
[Cc to Stas as the example in the guide is wrong, and Dave explains
the correct way]
On Mon, Jul 31, 2000 at 03:42:18PM -0400, Dave Moore took time to write:
duh...now that i've had some more coffee...the line:
PerlVersionINC On
must come before the PerlINC statement.
you arent doing anything wrong. you probably just need to upgrade to the
latest version of Apache::ExtUtils. this is not the same ExtUtils that
comes with mod_perl 1.24. you will have to get it from the latest cvs
snapshot of mod_perl. you will also have to remake/install PerlVINC after
you
duh...now that i've had some more coffee...the line:
PerlVersionINC On
must come before the PerlINC statement. PerlINC wont store that path
unless PerlVersionINC is On.
dave
On Mon, 31 Jul 2000, Dave Moore wrote:
you arent doing anything wrong. you probably just need to upgrade to the
Hi all,
(debian potato)
apache-ssl : 1.3.9.13-2
modperl : 1.21.2309-1
perl : 5.005
Apache::PerlVINC : 0.01 compiled by myself
As recommended in the guide, i'm trying to use Apache::PerlVINC since
I have 3 virtualhosts, and the same sets of modules for all three (same namespace), in
three
(PHP4.0), and PHP doing things with DBI that causes this segfault.
I tried to recompile my Apache without PHP, but the segfault is still
there...
Since it's ONLY DBI-connect that calls this segfault, I can't imagine it
beeing anything else BUT a but in some MySQL-libraries or perl-modules.
I'm getting
Ok...
If some information was missing in my previous mails, here it comes ;)
Apache version: 1.3.12
mod_perl version: 1.24
mod_php version: 4.0.0
MySQL version: Ver 9.38 Distrib 3.22.32, for pc-linux-gnu (i586)
Msql-Mysql modules version: 2.0414
DBI version: 1.14
HTML::Mason: 0.87
gdb dump:
(no
To: Trond Arve Nordheim
Cc: [EMAIL PROTECTED]
Subject: RE: Apache segfault
I can't confirm this. I use Apache 1.3.12, mod_perl 1.24, mod_php 4.0.xx,
MySQL 3.22.32 on a FreeBSD box and everything runs fine.
lg,
le
using Suse Linux 6.4,
are you?
lg,
le
-Original Message-
From: Lukas Ertl [mailto:[EMAIL PROTECTED]]
Sent: 18. juli 2000 14:05
To: Trond Arve Nordheim
Cc: [EMAIL PROTECTED]
Subject: RE: Apache segfault
I can't confirm this. I use Apache 1.3.12, mod_perl 1.24, mod_php 4.0.
Trond Arve Nordheim wrote, re the "segfault on DBI-connect" problem:
I found out that using all mod_perl-versions between 1.22 and 1.24 with DBI
causes this segfault (Thanks to obscurite, #linux@efnet :)
So, after downgrading my mod_perl to 1.21.3, everything works fine..
That was not the problem.
I've tried that on all 3 servers, without results...
- dufuz
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: 18. juli 2000 14:27
To: Trond Arve Nordheim
Cc: [EMAIL PROTECTED]
Subject: segfault on DBI-connect (was Re: Apache segfault
On Tue, 18 Jul 2000, Trond Arve Nordheim wrote:
Since it's ONLY DBI-connect that calls this segfault, I can't imagine
it beeing anything else BUT a but in some MySQL-libraries or
perl-modules. I'm getting kind of desperat here, so an answer would be
deeply appreciated :)
Have you tried
I had the segfault problem with Redhat 6.1/mod_perl 1.2x/php 4.0RC1
Then I upgraded to PHP4.0.1pl2, and upon configuring got this little handy
message:
++
|*** WARNING
On Tue, 18 Jul 2000, Drew Degentesh wrote:
I had the segfault problem with Redhat 6.1/mod_perl 1.2x/php 4.0RC1
Then I upgraded to PHP4.0.1pl2, and upon configuring got this little handy
message
Hi.
I'm having problems with my Apache segfaulting when I run subroutines from
modules that uses DBI. ([Mon Jul 17 13:55:22 2000] [notice] child pid 28327
exit signal Segmentation fault (11)).
It seems like the DBI-connection function causes this, but I'm not able to
find out why. It's actually
On Mon, 17 Jul 2000, Trond Arve Nordheim wrote:
Hi.
I'm having problems with my Apache segfaulting when I run subroutines from
modules that uses DBI. ([Mon Jul 17 13:55:22 2000] [notice] child pid 28327
exit signal Segmentation fault (11)).
It seems like the DBI-connection function causes
On Mon, 17 Jul 2000, Lukas Ertl wrote:
On Mon, 17 Jul 2000, Trond Arve Nordheim wrote:
Hi.
I'm having problems with my Apache segfaulting when I run subroutines from
modules that uses DBI. ([Mon Jul 17 13:55:22 2000] [notice] child pid 28327
exit signal Segmentation fault (11)).
It
Hi all,
Sorry, this is a bit long.
[snip]
[Fri Jun 16 17:20:21 2000] [notice] \
child pid 22310 exit signal Segmentation Fault (11)
[snip]
There is no core dump and the same thing happens with the -X switch.
please see the instructions in SUPPORT on how to provide a backtrace.
--
Eric
Hi Eric,
[Fri Jun 16 17:20:21 2000] [notice] \
child pid 22310 exit signal Segmentation Fault (11)
On Mon, 19 Jun 2000, Eric Cholet wrote:
backtrace.
(gdb) bt
#0 0x2b444 in perl_handler_ismethod ()
#1 0x2c43c in perl_call_handler ()
#2 0x2bd5c in perl_run_stacked_handlers ()
#3
to Apache::Request-new() and I
don't know why. I don't think that should make Apache segfault...
I searched the archives and there are some Solaris segfaults but
nothing seems to fit this simple case. I don't have access to the
machines at the weekend so I've posted this hoping it might ring some
On Tue, 6 Jun 2000, Damon Buckwalter wrote:
When using Apache::PerlRun to try and run some CGI-ish scripts I noticed a
strange phenomenon. If the shebang line in the script contains '-T', that
Apache child will segfault on requests to the script. Combinations of '-w',
nothing
On Fri, Jun 09, 2000 at 10:49:14AM -0700, Doug MacEachern wrote:
On Tue, 6 Jun 2000, Damon Buckwalter wrote:
When using Apache::PerlRun to try and run some CGI-ish scripts I noticed a
strange phenomenon. If the shebang line in the script contains '-T', that
Apache child will segfault
On Fri, 9 Jun 2000, Damon Buckwalter wrote:
I'm sorry, please excuse my previous laziness... Here's all the info I can
gather:
if you compile with PERL_DEGUG=1, the stacktrace will give more info.
looks like the call to Apache::warn, the problem probably goes away with
this bandaid.
---
When using Apache::PerlRun to try and run some CGI-ish scripts I noticed a
strange phenomenon. If the shebang line in the script contains '-T', that
Apache child will segfault on requests to the script. Combinations of '-w',
nothing in the shebang line and no shebang line at all work
I forgot to mention also that mod_perl is statically compiled into Apache,
and using Perl 5.6.0
--
OpenPGP public key: http://www.meta-x.net/damon/pubkey.asc
Running under httpd -X, first time through my subrequest goes fine, second
time through it segfaults. Here's the non-debugging bt:
Program received signal SIGSEGV, Segmentation fault.
0x8080757 in ap_copy_table ()
(gdb) bt
#0 0x8080757 in ap_copy_table ()
#1 0x80937ef in
Replying to my own post... I found the problem - I was caching a
subrequest in the child's memory and trying to call lookup_* again with
that cached request. Doesn't work for fairly obvious reasons.
On Fri, 2 Jun 2000, Matt Sergeant wrote:
Running under httpd -X, first time through my
It seems that Devel::Dprof and diagnostics can't live together. I wanted
to profile the code that uses diagnostics from within mod_perl, but it
segfaults with no core dumped and no error messages, so here is the gdb
trace. The code runs Ok from the command line and produce the right dump
file
When I pass an undef (or "", maybe) to Apache::Util-unescape_uri_info
it gives me segfault.
Any idea?
Kenneth
- PerlHandler -
package Apache::SegFault;
use Apache::Util qw(unescape_uri_info);
sub handler
{
my ($r) = shift;
$r-send_http_header("text/ht
On Mon, 22 May 2000, Roger Foskett (2) wrote:
MOD_PERL VERSION
mod_perl-1.23
- MOD_PERL CONFIGURATION
perl ./Makefile.PL \
USE_APXS=1 \
WITH_APXS=/usr/local/apache/bin/apxs \
EVERYTHING=1
thanks for the complete bug report, if only you
On Tue, 23 May 2000, Kenneth Lee wrote:
When I pass an undef (or "", maybe) to Apache::Util-unescape_uri_info
it gives me segfault.
Any idea?
i'm surprised this hasn't bitten anybody before. thanks for the
report, patch below.
--- src/modules/perl/Apache.xs 2000/04/21 06:03:5
On Sat, 20 May 2000, Matthew Darwin wrote:
My apache dies about 30% of the time when handling any mod_perl request
that requires XML::Parser. Any other page (even pages that use
mod_perl) are 100% ok.
Are there any known issues with this (besides the requirement for
Hello I have been having problems getting Apache (APXS build) working with
mod_perl. I get a segfault (printed in the errorlog) when clients try and
connect to apache.
All the components (perl, apache, mod_perl) are default clean builds (all
gcc) - the segfault (and apache hang) only occurs when
My apache dies about 30% of the time when handling any mod_perl request
that requires XML::Parser. Any other page (even pages that use
mod_perl) are 100% ok.
Are there any known issues with this (besides the requirement for
--disable-rule=expat)? This all worked fine with perl 5.005_03 +
Many of us have been experiencing segfaults on DBI-connect when using the
DBD-mysql
drivers.
I wonder if anyone has found a solution.
I've appended a pretty comprehensive overview of the problem below.
Problem description: Child Apache process segfaults on DBI-connect with
Apache
1.3.12 and
Michael Poole wrote:
In hopes that this would fix the APXS build, I tried rebuilding with
that, but whenever the httpd tried to load the php3 or perl module, it
would die in pthread_mutex_lock. This was slightly odd, since php3
would load fine when httpd was statically linked against
can you see if this patch fixes the problem? make sure you let mod_perl
build httpd and pass USE_APACI=1 to Makefile.PL
--- Makefile.PL 2000/04/21 06:24:27 1.158
+++ Makefile.PL 2000/04/27 22:45:30 1.160
@@ -186,7 +186,7 @@
$PERL_DEBUG = "";
$PERL_DESTRUCT_LEVEL = "";
Doug MacEachern [EMAIL PROTECTED] writes:
perl Makefile.PL USE_APXS=1 WITH_APXS=/usr/local/sbin/apxs EVERYTHING=1
probably a long shot, but any difference if you build with USE_DSO=1
instead of USE_APXS ?
My apologies for taking so long to reply -- it's been a busy week.
From a clean
Doug MacEachern [EMAIL PROTECTED] writes:
can you see if this patch fixes the problem? make sure you let mod_perl
build httpd and pass USE_APACI=1 to Makefile.PL
--- Makefile.PL 2000/04/21 06:24:27 1.158
+++ Makefile.PL 2000/04/27 22:45:30 1.160
@@ -186,7 +186,7 @@
$PERL_DEBUG
Doug MacEachern [EMAIL PROTECTED] writes:
On 22 Apr 2000, Michael Poole wrote:
I get a segfault on the first page access to Apache (it's just a
request for / on the server). Backtrace:
...
That line of mod_perl.c is "dPPDIR;"
However, r-per_dir_config i
perl Makefile.PL USE_APXS=1 WITH_APXS=/usr/local/sbin/apxs EVERYTHING=1
probably a long shot, but any difference if you build with USE_DSO=1
instead of USE_APXS ?
I get a segfault on the first page access to Apache (it's just a
request for / on the server). Backtrace:
#0 0x402307db in perl_header_parser (r=0x8154e84) at mod_perl.c:1002
#1 0x8052715 in run_method (r=0x8154e84, offset=58, run_all=1)
at http_config.c:360
#2 0x8052802
On Sun, 16 Apr 2000, Jochen Wiedmann wrote:
Btw, Doug, as I see the sigpipe thing: What do you recommend for the
DBD::mysql driver? (Remember the "MySQL morning bug"?) Should we
enable or disable SIGPIPE?
apache no longer catches SIGPIPE as of 1.3.6, so it may not be an issue
anymore if
On Tue, 18 Apr 2000, DeWitt Clinton wrote:
On Tue, Apr 18, 2000 at 12:43:57PM -0400, Delaporta, Michael wrote:
I'm currently using XML::Parser (2.28) under Apache (1.3.11) and
mod_perl (1.21) and have noticed a fairly large number of segfaults in
the Apache error_log.
I noticed a
I'm currently using XML::Parser (2.28) under Apache (1.3.11) and
mod_perl (1.21) and have noticed a fairly large number of segfaults in
the Apache error_log.
I noticed a discussion about this problem on the list about a week ago,
but the only solution posted was as a Debian package (which I
Drew Degentesh wrote:
Below is a backtrace of my segfault received on DBI-Connect (sorry but my
perl and apache binaries are stripped)... you can see that mysql_close is
being called with a null argument, rather than mysql_real_connect as
indicated in some of the other backtraces reported
from the mod_perl mailing list, but that I haven't
verified yet.) Calling mysql_real_connect with mysql==NULL will surely
cause a SEGFAULT.
I'm using:
Redhat 6.1 (Linux 2.2.12-20RS )
Apache/1.3.12 (from distribution)
mod_perl: 1.22 (compiled from source, running as a DSO
On Tue, 11 Apr 2000, Doug MacEachern wrote:
On Tue, 4 Apr 2000 [EMAIL PROTECTED] wrote:
I've been seeing the same segfault-on-connect problem with Apache 1.2.12
+ mod_perl 1.22 + DBI 1.13 + Msql-Mysql-modules 1.2211. The segfault is
due to a null first argument being passed
Fickle, fickle machines.
The segfault problem with Embperl and Apache::Session can be fixed with about 3
keystrokes in emacs.
When I was getting the segfault error I had:
# BEGIN EMBPERL SESSION HANDLING
PerlSetEnv EMBPERL_SESSION_CLASSES "DBIStore SysVSemaphoreLocker"
Gerald, if it's not on the wish list already, could you add a
request for the
ability to set nsems in EMBPERL_SESSION_ARGS. Or maybe I should
just get off my
butt and make a patch.
This works already. You can give any arguments to EMBPERL_SESSION_ARGS that
a Store or Locker module
I have a nasty feeling this might be the RULE_EXPAT thing, I didn't do a
RULE_EXPAT=no when building Apache. Is there documentation describing the
dirty details of the issue? Can anybody confirm?
Program received signal SIGSEGV, Segmentation fault.
__pthread_mutex_lock (mutex=0x410) at
On 13-Apr-2000 Gerald Richter wrote:
Trying to use Apache::Session with Embperl 1.2.1, mod_perl 1.21,
Apache 1.3.9.
I've got this running on another machine just fine with the exact
same setup (I
think).
When I try access an Embperl page that uses %udat I get:
[Thu Apr 13 14:51:05 2000]
On 13-Apr-2000 Mark Ng wrote:
can you tell me the following about your 2 systems (the one that works and
the new
one), I have the same problem.
I need to know:
Versions of: Perl
Both are 5.004_04
apache
Both are 1.3.9
modperl
Both are 1.21
embperl
Both are 1.2.1
OS (Exact
On Thu, 13 Apr 2000, Shevek wrote:
I have a nasty feeling this might be the RULE_EXPAT thing, I didn't do a
RULE_EXPAT=no when building Apache. Is there documentation describing the
dirty details of the issue? Can anybody confirm?
well, are you using XML::Parser? if so, why not confirm
Trying to use Apache::Session with Embperl 1.2.1, mod_perl 1.21,
Apache 1.3.9.
I've got this running on another machine just fine with the exact
same setup (I
think).
When I try access an Embperl page that uses %udat I get:
[Thu Apr 13 14:51:05 2000] [notice] Apache/1.3.9 (Unix)
If you tell me what to do I'll try to get a stack backtrace.
http://perl.apache.org/embperl/Faq.pod.1.html#make_test_fails_with_a_SIG
_
Gerald
#0 0xff1d7540 in Perl_sv_clear ()
from
/opt/gnu/depot/perl5.004_04/lib/sun4-solaris/5.00404/CORE/libperl.so
It crashs somewhere deep inside of Perl, so it's hard to say what's happeing
here.
I would first try to recompile all modules (maybe Perl itself also), to make
sure things fit
On Thu, 13 Apr 2000, Jason Bodnar wrote:
Hmmm ... maybe it's a problem with Solaris 5.7?
Can you try the binaries from the 2.6 box on the 2.7 box to see if that
works? That would at least kind of indicate whether it's an OS bug or a
configuration bug.
-Mark
The binaries on both boxes are the same. They get rdist'd out from one
machine every night.
I'm going to rebuild the latest versions of everything on the 2.7 machine
tomorrow and see if that makes a difference.
At 10:57 PM 4/13/00 -0400, Mark Imbriaco wrote:
On Thu, 13 Apr 2000, Jason Bodnar
Trying to use Apache::Session with Embperl 1.2.1, mod_perl 1.21, Apache 1.3.9.
I've got this running on another machine just fine with the exact same setup (I
think).
I created a db called sessions with a table called sessions:
mysql show fields from sessions;
this copy-n-paste from ~/Mail/.sent-mail-dec-1999 might help:
---
a few things could shed some more light:
build a libperld.a and compile with PERL_DEBUG=1 (see SUPPORT doc)
and/or, in gdb:
(gdb) source mod_perl-1.21/.gdbinit
(gdb) curinfo
should tell you the line/filename of the offending
this seems to becoming quite a common problem, i wonder if Jochen can shed
some light?
On Tue, 4 Apr 2000 [EMAIL PROTECTED] wrote:
I've been seeing the same segfault-on-connect problem with Apache 1.2.12
+ mod_perl 1.22 + DBI 1.13 + Msql-Mysql-modules 1.2211. The segfault is
due to a null
Hi,
after some browsing of the [EMAIL PROTECTED] archives, I see now that my
AuthDBI problem is the same as this thread (Segfault on DBI-Connect). I
tried the workaround suggested by wil (*sock=0 before mysql_init(sock)) to
no avail.
Here's a backtrace from gdb httpd -X. Has any headway been
for the MySQL struct pointed to
by "MySQL *", if the pointer is null, it'll allocate mem for it.
I'm still experimenting, don't know if this will break anything else!!!
So use with care!!
wil.
--- original message ---
Subject: Re: Segfault on DBI-Connect
Author: [EMAIL PROTE
We seem to be dancing around the DBI-connect segfault problem with MySQL
DBI drivers. Maybe someone here who reads other relevant lists could for-
ward our traffic and see if we can create some synergy there.
Our basic story is that, with Apache 1.3.12 and mod_perl 1.22 (with DBI
version 1.13
From: James G Smith [EMAIL PROTECTED]
Reply-To: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
CC: Valter Mazzola [EMAIL PROTECTED], Doug MacEachern
[EMAIL PROTECTED]
Subject: Re: Segfault on DBI-Connect
Date: Mon, 03 Apr 2000 00:13:14 -0500
Doug MacEachern [EMAIL PROTECTED] wrote:
On Sat, 1 Apr
I've been seeing the same segfault-on-connect problem with Apache 1.2.12
+ mod_perl 1.22 + DBI 1.13 + Msql-Mysql-modules 1.2211. The segfault is
due to a null first argument being passed to mysql_real_connect().
Running Apache with a -X argument yields the following backtrace when my
mod_perl
On Sat, 1 Apr 2000, Valter Mazzola wrote:
i've a mod_perl script that connect to a mysql db, but sometimes it segfault
on DBI-connect. i'm using Apache::Registry Apache::DBI for persistend db
connection, use strict and the script it's a package. i've read the docs but
probably i'm
Doug MacEachern [EMAIL PROTECTED] wrote:
On Sat, 1 Apr 2000, Valter Mazzola wrote:
i've a mod_perl script that connect to a mysql db, but sometimes it segfault
on DBI-connect. i'm using Apache::Registry Apache::DBI for persistend db
connection, use strict and the script it's a package
i've a mod_perl script that connect to a mysql db, but sometimes it segfault
on DBI-connect. i'm using Apache::Registry Apache::DBI for persistend db
connection, use strict and the script it's a package. i've read the docs but
probably i'm missing something.
The persistent DBI connection
On Wed, 29 Mar 2000, Shevek wrote:
I can't find any documentation for what RULE_EXPAT does, the only
occurrence at all is in Apache src/Configure, where it seels to compile in
the expat lite library.
RULE_EXPAT=no disables the expat lite library. there have been reports of
it clashing with
developed the code quite a way past that segfault, although I
have had several more reproducible ones, mostly related to some particular
feature ofmy Perl.
S.
On Tue, 28 Mar 2000, Doug MacEachern wrote:
On Fri, 24 Mar 2000, Shevek wrote:
Now we get rid of the DOM tree.
44
On Fri, 24 Mar 2000, Shevek wrote:
Now we get rid of the DOM tree.
44 $document-dispose;
And the child segfaults. But if I don't have the dumper, that does not
happen. What is the best way to get around this? Is undefining $d an
appropriate technique?
did you configure
try building Perl with Configure -Uusemymalloc, solaris+perl malloc don't
seem to get along when mod_perl is a dso. you're better off to link
static though, solaris system malloc is 25%-30% slower than using Perl's
malloc
On Mon, 18 Oct 1999, Steve Snodgrass wrote:
I've been using mod_perl
I've been using mod_perl with Raven's SSL package for some time now, but I'm
building a refresh of our environment with new versions of everything and I
ran into trouble. I decided to use APXS this time instead of building
mod_perl statically. Everything compiled and installed fine but Apache
101 - 176 of 176 matches
Mail list logo