Hello,
I am having problems with Embperl 2.2.0 under SuSe 10. The system is an
x86_64, running Linux 2.6.13, Apache 1.3.34 and mod_perl 1.29.
I am running a very simple page which results in a segmentation fault,
but most of the time the page returns successfully.
From the error_log:
[Sun Ju
>
> Gerald Richter wrote:
> >>Version of embperl is 2.0.0, mod_perl 2.0.1, apache 2.0.54 (prefork
> >>mpm only), perl 5.8.4.
> >>
> >>Any ideas ?
> >>
> >
> >
> > How does your httpd.conf look like?
> >
> > Did you load the C part with LoadModule and the Perl part (with
> > PerlModule or use)
Gerald Richter wrote:
>>Version of embperl is 2.0.0, mod_perl 2.0.1, apache 2.0.54
>>(prefork mpm only), perl 5.8.4.
>>
>>Any ideas ?
>>
>
>
> How does your httpd.conf look like?
>
> Did you load the C part with LoadModule and the Perl part (with PerlModule
> or use) both on startup?
using Per
>
> Version of embperl is 2.0.0, mod_perl 2.0.1, apache 2.0.54
> (prefork mpm only), perl 5.8.4.
>
> Any ideas ?
>
How does your httpd.conf look like?
Did you load the C part with LoadModule and the Perl part (with PerlModule
or use) both on startup?
Gerald
Am 20.09.2005 um 11:58 schrieb Alvaro Lopes:
Hi list
I'm having some technical problems with embperl. When apache2
handles a
second request, the child dies with segmentation fault. The first
request is processed fine. I was able to do a backtrace using gdb and
httpd -X (the signal handler s
Hi list
I'm having some technical problems with embperl. When apache2 handles a
second request, the child dies with segmentation fault. The first
request is processed fine. I was able to do a backtrace using gdb and
httpd -X (the signal handler shown in #3 was installed by me to handle
SIGSEGV):
ent: August 10, 2003 2:33 PM
> To: Justin Harrison; [EMAIL PROTECTED]
> Subject: Re: Segmentation faults...
>
> >
> > What is the best way to debug segmentation faults? Randomly
> all of my
> > apache children are segfaulting. I am fairly certain this is due to
>
>
> What is the best way to debug segmentation faults? Randomly all of my
> apache children are segfaulting. I am fairly certain this is due to some
> Embperl code being ran, but I don't know where to look, or how to start
> looking...
>
First of all compile Embperl with
Harrison wrote:
> Hi,
>
> What is the best way to debug segmentation faults? Randomly all of my apache
> children are segfaulting. I am fairly certain this is due to some Embperl
> code being ran, but I don't know where to look, or how to start lo
Hi,
What is the best way to debug segmentation faults? Randomly all of my apache
children are segfaulting. I am fairly certain this is due to some Embperl
code being ran, but I don't know where to look, or how to start looking...
J
>
> Yes it does. I'm certain it does.
If make test is ok, we need a stackbacktrace. Compile Embperl with debug
support
perl Makefile.PL debug
make install
then start gdb
gdb /path/to/httpd
set args -f /path/to/your/httpd.conf -X
r
-> Now request the page that segfaults, after gdb reports the
--- Gerald Richter <[EMAIL PROTECTED]> wrote:
>
>
> > EMBPERL_SESSION_MODE 2
> >
> > Was the killer argument. With it commented out,
> all
> > works fine. So the problem must lie with
> > Apache::SessionX
>
> Does make test work correctly? If not we should
> solve this first, because
> make
> (you haven't said what DBD driver you're using)
DBD::mysql
I'll try tuning the database cleanup.
Thanks for the ideas.
-Jarrod
__
Do You Yahoo!?
Yahoo! Finance - Get real-time stock quotes
http://finance.yahoo.com
-
At Thu, 22 Aug 2002 07:03:40 -0700 (PDT), Jarrod Stenberg wrote:
> Does not have any problems. This file uses this:
> [$ while ($h = $sth->fetchrow_hashref()) $]
> [$ endwhile $]
>
> But call it from the browser, and it kills the httpd
> instance.
(you haven't said what DBD driver you're using)
> EMBPERL_SESSION_MODE 2
>
> Was the killer argument. With it commented out, all
> works fine. So the problem must lie with
> Apache::SessionX
>
Does make test work correctly? If not we should solve this first, because
make test should test all this things and show us what goes wrong...
Gera
> PerlModule Embperl
> PerlModule DBI
> PerlModule DBD::whatever_you_use
>
> Does this change anything? If not would be nice to
> get a stackbacktrace from
> Apache. Start Apache with -X option to debug.
I had to add:
PerModule DBD::mysql
Tried it, and it still faulted. Starting apache with
> embpexec.pl drawCompressed.htm "yr=2002&mo=08"
>
> Does not have any problems. This file uses this:
> [$ while ($h = $sth->fetchrow_hashref()) $]
> [$ endwhile $]
>
> But call it from the browser, and it kills the httpd
> instance.
>
Please make sure you have loaded DBI & Embperl at the serv
embpexec.pl drawCompressed.htm "yr=2002&mo=08"
Does not have any problems. This file uses this:
[$ while ($h = $sth->fetchrow_hashref()) $]
[$ endwhile $]
But call it from the browser, and it kills the httpd
instance.
FTR, both use the same perl. I have check and
double-checked this. So they
>
> Mmmh, Embperl 2 should generate the same Perl code
> for both of these
> examples. Maybe it's related to the "do stuff" part?
> If you not already done
> so please make that part very simple, for example
> just a $i++ . Does it
> still crash?
It does not matter what I put in the block. For
> So, of course I should move to XHTML as a good
> practice, but is the unclosed tag thing something that
> could cause Embperl to go nuts in 2.0b8?
>
Embperl doesn't care about if you close your tags or not. The only exception
are table tags that are used for build dynamic tables, but it will no
More info.
I discovered that the segfaults are related to DBI.
Given:
# DBI is already loaded.
$dbh = ...
$sth = $dbh->prepare(...);
$sth->execute();
And the above is a successful query leaving me a
handle with stuff to do. If I do this:
while ($h = $sth->fetchrow_hashref()) {
#
More info.
I discovered that the segfaults are related to DBI.
Given:
If I do this:
while ($h = $sth->fetchrow_hashref()) {
#do stuff
}
within the same block, it works fine.
But, if I do this:
[$ while ($h = $sth->fetchrow_hashref()) $]
__
I'm trying to get to the bottom of trouble with a web
application that runs out of control and crashes the
apache children (Apache/1.3.26 on 4.6.2-RELEASE with
perl 5.6.1 [ all of my perl modules have been rebuilt
with 5.6.1 which seems to be a good idea on FreeBSD
]).
Not everything crashes, but
23 matches
Mail list logo
