Mailing List Archive

>
> I noticed segfaults in my error logs a couple days ago. I am
> getting 1 for about every 1K page views. I am able to
> reproduce it now, but still can't make any sense of it. I'm
> sending a backtrace, and my environment.
>

I will send you my current development version per private mail, because it
contains some more checks for out of memory conditions.

Please install it with

perl Makefile.pl debug
make
make install

This will give additional informations in the backtrace, in case the the
segfault happens again. If you still get the segfault, please send me the
backtrace again

Gerald




** Virus checked by BB-5000 Mailfilter **


---------------------------------------------------------------------
To unsubscribe, e-mail: embperl-unsubscribe@perl.apache.org
For additional commands, e-mail: embperl-help@perl.apache.org

Thanks,

I have continued testing, and I can confidently say that the problem is definitely not an out-of-memory issue. The new dev version you sent is segfaulting about once for every 100 page requests in dev now, with no load except me clicking around, on a machine with 2G total RAM and plenty of free memory.

The segfaults have occurred during pretty much every type of page request, and also not occurred on those same requests. Hitting refresh will always result in the page being correctly sent, with not segfault, on at most a couple pushes.

Did you get the back-traces I sent? I sent them to your personal account, but I realized that you may check the list more. Every back-trace points to "EMBPERL2_Node_appendChild .... at epdom.c:2835" as the point of segfaulting.

The only Embperl tags I ever use are the PerlBlock '[* *], [+ +], [- -]' tags. Is there someway I can bypass this 'epdom' code all together? (I don't see any reason for dom-parsing)

This is pretty scary.

Thanks,

-Carl

----- Original Message ----
From: Gerald Richter <richter@ecos.de>
To: BeeThere Admin <carl@beesw.com>; embperl@perl.apache.org
Sent: Wednesday, March 15, 2006 11:28:50 PM
Subject: RE: Intermittent Segfaults


>
> I noticed segfaults in my error logs a couple days ago. I am
> getting 1 for about every 1K page views. I am able to
> reproduce it now, but still can't make any sense of it. I'm
> sending a backtrace, and my environment.
>

I will send you my current development version per private mail, because it
contains some more checks for out of memory conditions.

Please install it with

perl Makefile.pl debug
make
make install

This will give additional informations in the backtrace, in case the the
segfault happens again. If you still get the segfault, please send me the
backtrace again

Gerald




** Virus checked by BB-5000 Mailfilter **

---------------------------------------------------------------------
To unsubscribe, e-mail: embperl-unsubscribe@perl.apache.org
For additional commands, e-mail: embperl-help@perl.apache.org

>
> I have continued testing, and I can confidently say that the
> problem is definitely not an out-of-memory issue.

ok

> The new dev
> version you sent is segfaulting about once for every 100 page
> requests in dev now, with no load except me clicking around,
> on a machine with 2G total RAM and plenty of free memory.
>
> The segfaults have occurred during pretty much every type of
> page request, and also not occurred on those same requests.
> Hitting refresh will always result in the page being
> correctly sent, with not segfault, on at most a couple pushes.
>
> Did you get the back-traces I sent?

Yes. These backtraces are with the new version I sent, right? (I need to
make sure the line numbers of the backtrace matches my source)

> I sent them to your
> personal account, but I realized that you may check the list
> more. Every back-trace points to "EMBPERL2_Node_appendChild
> .... at epdom.c:2835" as the point of segfaulting.
>
> The only Embperl tags I ever use are the PerlBlock '[* *], [+
> +], [- -]' tags. Is there someway I can bypass this 'epdom'
> code all together? (I don't see any reason for dom-parsing)
>

This code also parses [..] tags, so you will need it. (It never builds a
full dom tree of your source, it only parses out the tags that you tell
Embperl to process)

I have to take a deeper look at the backtraces. I will come back to you as
soon as possible

Gerald





** Virus checked by BB-5000 Mailfilter **


---------------------------------------------------------------------
To unsubscribe, e-mail: embperl-unsubscribe@perl.apache.org
For additional commands, e-mail: embperl-help@perl.apache.org

I just found out that I have segfaults on my servers too.
OS is debian testing
The apache startup message should include all infos you might want to know too:
[Mon Mar 20 18:27:05 2006] [notice] Apache/2.0.55 (Debian) Embperl/2.1.0 mod_ssl/2.0.55 OpenSSL/0.9.8a mod_apreq2-20051231/2.5.7 mod_perl/2.0.2 Perl/v5.8.8 configured -- resuming normal operations

I've recompiled Embperl today to make sure it uses the current software versions but that didn't help.

-Alex


-----Original Message-----
From: Gerald Richter [mailto:richter@ecos.de]
Sent: Friday, March 17, 2006 9:16 PM
To: 'BeeThere Admin'; embperl@perl.apache.org
Subject: RE: Intermittent Segfaults


>
> I have continued testing, and I can confidently say that the
> problem is definitely not an out-of-memory issue.

ok

> The new dev
> version you sent is segfaulting about once for every 100 page
> requests in dev now, with no load except me clicking around,
> on a machine with 2G total RAM and plenty of free memory.
>
> The segfaults have occurred during pretty much every type of
> page request, and also not occurred on those same requests.
> Hitting refresh will always result in the page being
> correctly sent, with not segfault, on at most a couple pushes.
>
> Did you get the back-traces I sent?

Yes. These backtraces are with the new version I sent, right? (I need to
make sure the line numbers of the backtrace matches my source)

> I sent them to your
> personal account, but I realized that you may check the list
> more. Every back-trace points to "EMBPERL2_Node_appendChild
> .... at epdom.c:2835" as the point of segfaulting.
>
> The only Embperl tags I ever use are the PerlBlock '[* *], [+
> +], [- -]' tags. Is there someway I can bypass this 'epdom'
> code all together? (I don't see any reason for dom-parsing)
>

This code also parses [..] tags, so you will need it. (It never builds a
full dom tree of your source, it only parses out the tags that you tell
Embperl to process)

I have to take a deeper look at the backtraces. I will come back to you as
soon as possible

Gerald





** Virus checked by BB-5000 Mailfilter **


---------------------------------------------------------------------
To unsubscribe, e-mail: embperl-unsubscribe@perl.apache.org
For additional commands, e-mail: embperl-help@perl.apache.org



*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*
T-Systems Austria GesmbH
Rennweg 97-99, 1030 Wien
Telefon +43 (0)57057 0, Telefax +43 (0)57057 8155
Bank Austria AG, BLZ 12000, Kto. 233-111-674/00, IBAN AT291200023311167400
Handelsgericht Wien, FN 79340b – DVR Nr. 0713520 – ARA-Lizenz Nr. 12554
ATU 15169001

*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*
Hinweis: Dieses E-mail kann vertrauliche und geschützte Informationen enthalten.
Sollten Sie nicht der beabsichtigte Empfänger sein, verständigen Sie bitte den Absender und löschen Sie dieses E-mail dann sofort.

Notice: This e-mail contains information that is confidential and may be privileged.
If you are not the intended recipient, please notify the sender and then delete this e-mail immediately.
*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*

I don't know the details, it seems to be a pretty general problem. Gerald seems to be on it though. He even said that he was working through the weekend (bless his heart :-)

The symptom on the user side, at least for me is a completely blank page. It looks like the server sends back a 200 OK, but then nothing else. There doesn't seem to be any way to debug the problem at the Embperl-user side because none of the page code ever gets executed, not even your base.epl (or whatever you call it). A page refresh will usually result in the expected page rendering, but at least for us, this is a critical issue holding a major release, business deals, etc.

I looked into the logs because a user told me they couldn't get into a section of the site because they only got a blank page. The page seems to be random, but I can easily reproduce the problem in my dev environment now.

FYI,

-Carl

Bee Software LLC
See us in action at: http://beethere.net/

----- Original Message ----
From: Hartmaier Alexander <Alexander.Hartmaier@t-systems.at>
To: embperl@perl.apache.org
Sent: Monday, March 20, 2006 12:50:29 PM
Subject: RE: Intermittent Segfaults


I just found out that I have segfaults on my servers too.
OS is debian testing
The apache startup message should include all infos you might want to know too:
[Mon Mar 20 18:27:05 2006] [notice] Apache/2.0.55 (Debian) Embperl/2.1.0 mod_ssl/2.0.55 OpenSSL/0.9.8a mod_apreq2-20051231/2.5.7 mod_perl/2.0.2 Perl/v5.8.8 configured -- resuming normal operations

I've recompiled Embperl today to make sure it uses the current software versions but that didn't help.

-Alex


-----Original Message-----
From: Gerald Richter [mailto:richter@ecos.de]
Sent: Friday, March 17, 2006 9:16 PM
To: 'BeeThere Admin'; embperl@perl.apache.org
Subject: RE: Intermittent Segfaults


>
> I have continued testing, and I can confidently say that the
> problem is definitely not an out-of-memory issue.

ok

> The new dev
> version you sent is segfaulting about once for every 100 page
> requests in dev now, with no load except me clicking around,
> on a machine with 2G total RAM and plenty of free memory.
>
> The segfaults have occurred during pretty much every type of
> page request, and also not occurred on those same requests.
> Hitting refresh will always result in the page being
> correctly sent, with not segfault, on at most a couple pushes.
>
> Did you get the back-traces I sent?

Yes. These backtraces are with the new version I sent, right? (I need to
make sure the line numbers of the backtrace matches my source)

> I sent them to your
> personal account, but I realized that you may check the list
> more. Every back-trace points to "EMBPERL2_Node_appendChild
> .... at epdom.c:2835" as the point of segfaulting.
>
> The only Embperl tags I ever use are the PerlBlock '[* *], [+
> +], [- -]' tags. Is there someway I can bypass this 'epdom'
> code all together? (I don't see any reason for dom-parsing)
>

This code also parses [..] tags, so you will need it. (It never builds a
full dom tree of your source, it only parses out the tags that you tell
Embperl to process)

I have to take a deeper look at the backtraces. I will come back to you as
soon as possible

Gerald





** Virus checked by BB-5000 Mailfilter **


---------------------------------------------------------------------
To unsubscribe, e-mail: embperl-unsubscribe@perl.apache.org
For additional commands, e-mail: embperl-help@perl.apache.org



*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*
T-Systems Austria GesmbH
Rennweg 97-99, 1030 Wien
Telefon +43 (0)57057 0, Telefax +43 (0)57057 8155
Bank Austria AG, BLZ 12000, Kto. 233-111-674/00, IBAN AT291200023311167400
Handelsgericht Wien, FN 79340b DVR Nr. 0713520 ARA-Lizenz Nr. 12554
ATU 15169001

*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*
Hinweis: Dieses E-mail kann vertrauliche und geschtzte Informationen enthalten.
Sollten Sie nicht der beabsichtigte Empfnger sein, verstndigen Sie bitte den Absender und lschen Sie dieses E-mail dann sofort.

Notice: This e-mail contains information that is confidential and may be privileged.
If you are not the intended recipient, please notify the sender and then delete this e-mail immediately.
*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*

---------------------------------------------------------------------
To unsubscribe, e-mail: embperl-unsubscribe@perl.apache.org
For additional commands, e-mail: embperl-help@perl.apache.org

Hi,

Could you please give the attached patch a try and let me know if it fixes
the segfaults.

Gerald


---------------------------------------------------------------------------
Gerald Richter ecos electronic communication services gmbh
IT-Securitylösungen * Webapplikationen mit Apache/Perl/mod_perl/Embperl

Post: Tulpenstrasse 5 D-55276 Dienheim b. Mainz
E-Mail: richter@ecos.de Voice: +49 6133 939-122
WWW: http://www.ecos.de/ Fax: +49 6133 939-333
---------------------------------------------------------------------------
ECOS BB-5000 Firewall- und IT-Security Appliance: www.bb-5000.info
---------------------------------------------------------------------------



> -----Original Message-----
> From: BeeThere Admin [mailto:admin@beethere.net]
> Sent: Tuesday, March 21, 2006 12:38 AM
> To: Hartmaier Alexander; embperl@perl.apache.org
> Subject: Re: Intermittent Segfaults
>
> I don't know the details, it seems to be a pretty general
> problem. Gerald seems to be on it though. He even said that
> he was working through the weekend (bless his heart :-)
>
> The symptom on the user side, at least for me is a completely
> blank page. It looks like the server sends back a 200 OK, but
> then nothing else. There doesn't seem to be any way to debug
> the problem at the Embperl-user side because none of the page
> code ever gets executed, not even your base.epl (or whatever
> you call it). A page refresh will usually result in the
> expected page rendering, but at least for us, this is a
> critical issue holding a major release, business deals, etc.
>
> I looked into the logs because a user told me they couldn't
> get into a section of the site because they only got a blank
> page. The page seems to be random, but I can easily reproduce
> the problem in my dev environment now.
>
> FYI,
>
> -Carl
>
> Bee Software LLC
> See us in action at: http://beethere.net/
>
> ----- Original Message ----
> From: Hartmaier Alexander <Alexander.Hartmaier@t-systems.at>
> To: embperl@perl.apache.org
> Sent: Monday, March 20, 2006 12:50:29 PM
> Subject: RE: Intermittent Segfaults
>
>
> I just found out that I have segfaults on my servers too.
> OS is debian testing
> The apache startup message should include all infos you might
> want to know too:
> [Mon Mar 20 18:27:05 2006] [notice] Apache/2.0.55 (Debian)
> Embperl/2.1.0 mod_ssl/2.0.55 OpenSSL/0.9.8a
> mod_apreq2-20051231/2.5.7 mod_perl/2.0.2 Perl/v5.8.8
> configured -- resuming normal operations
>
> I've recompiled Embperl today to make sure it uses the
> current software versions but that didn't help.
>
> -Alex
>
>
> -----Original Message-----
> From: Gerald Richter [mailto:richter@ecos.de]
> Sent: Friday, March 17, 2006 9:16 PM
> To: 'BeeThere Admin'; embperl@perl.apache.org
> Subject: RE: Intermittent Segfaults
>
>
> >
> > I have continued testing, and I can confidently say that the
> > problem is definitely not an out-of-memory issue.
>
> ok
>
> > The new dev
> > version you sent is segfaulting about once for every 100 page
> > requests in dev now, with no load except me clicking around,
> > on a machine with 2G total RAM and plenty of free memory.
> >
> > The segfaults have occurred during pretty much every type of
> > page request, and also not occurred on those same requests.
> > Hitting refresh will always result in the page being
> > correctly sent, with not segfault, on at most a couple pushes.
> >
> > Did you get the back-traces I sent?
>
> Yes. These backtraces are with the new version I sent, right?
> (I need to
> make sure the line numbers of the backtrace matches my source)
>
> > I sent them to your
> > personal account, but I realized that you may check the list
> > more. Every back-trace points to "EMBPERL2_Node_appendChild
> > .... at epdom.c:2835" as the point of segfaulting.
> >
> > The only Embperl tags I ever use are the PerlBlock '[* *], [+
> > +], [- -]' tags. Is there someway I can bypass this 'epdom'
> > code all together? (I don't see any reason for dom-parsing)
> >
>
> This code also parses [..] tags, so you will need it. (It
> never builds a
> full dom tree of your source, it only parses out the tags
> that you tell
> Embperl to process)
>
> I have to take a deeper look at the backtraces. I will come
> back to you as
> soon as possible
>
> Gerald
>
>
>
>
>
> ** Virus checked by BB-5000 Mailfilter **
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: embperl-unsubscribe@perl.apache.org
> For additional commands, e-mail: embperl-help@perl.apache.org
>
>
>
> *"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"
> *"*"*"*"*"*"*"*
> T-Systems Austria GesmbH
> Rennweg 97-99, 1030 Wien
> Telefon +43 (0)57057 0, Telefax +43 (0)57057 8155
> Bank Austria AG, BLZ 12000, Kto. 233-111-674/00, IBAN
> AT291200023311167400
> Handelsgericht Wien, FN 79340b DVR Nr. 0713520 ARA-Lizenz Nr. 12554
> ATU 15169001
>
> *"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"
> *"*"*"*"*"*"*"*
> Hinweis: Dieses E-mail kann vertrauliche und geschtzte
> Informationen enthalten.
> Sollten Sie nicht der beabsichtigte Empfnger sein,
> verstndigen Sie bitte den Absender und lschen Sie dieses
> E-mail dann sofort.
>
> Notice: This e-mail contains information that is confidential
> and may be privileged.
> If you are not the intended recipient, please notify the
> sender and then delete this e-mail immediately.
> *"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"
> *"*"*"*"*"*"*"*
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: embperl-unsubscribe@perl.apache.org
> For additional commands, e-mail: embperl-help@perl.apache.org
>
>
>
> ** Virus checked by BB-5000 Mailfilter **
> !DSPAM:4420651d76673852268083!
>



** Virus checked by BB-5000 Mailfilter **

I'm on it. I should have an answer in an hour or so.

Thank you!

-Carl

See us in action at: http://beethere.net/


----- Original Message ----
From: Gerald Richter <richter@ecos.de>
To: BeeThere Admin <carl@beesw.com>; Hartmaier Alexander <Alexander.Hartmaier@t-systems.at>; embperl@perl.apache.org
Sent: Tuesday, March 21, 2006 11:53:38 PM
Subject: RE: Intermittent Segfaults


Hi,

Could you please give the attached patch a try and let me know if it fixes
the segfaults.

Gerald


---------------------------------------------------------------------------
Gerald Richter ecos electronic communication services gmbh
IT-Securitylösungen * Webapplikationen mit Apache/Perl/mod_perl/Embperl

Post: Tulpenstrasse 5 D-55276 Dienheim b. Mainz
E-Mail: richter@ecos.de Voice: +49 6133 939-122
WWW: http://www.ecos.de/ Fax: +49 6133 939-333
---------------------------------------------------------------------------
ECOS BB-5000 Firewall- und IT-Security Appliance: www.bb-5000.info
---------------------------------------------------------------------------



> -----Original Message-----
> From: BeeThere Admin [mailto:admin@beethere.net]
> Sent: Tuesday, March 21, 2006 12:38 AM
> To: Hartmaier Alexander; embperl@perl.apache.org
> Subject: Re: Intermittent Segfaults
>
> I don't know the details, it seems to be a pretty general
> problem. Gerald seems to be on it though. He even said that
> he was working through the weekend (bless his heart :-)
>
> The symptom on the user side, at least for me is a completely
> blank page. It looks like the server sends back a 200 OK, but
> then nothing else. There doesn't seem to be any way to debug
> the problem at the Embperl-user side because none of the page
> code ever gets executed, not even your base.epl (or whatever
> you call it). A page refresh will usually result in the
> expected page rendering, but at least for us, this is a
> critical issue holding a major release, business deals, etc.
>
> I looked into the logs because a user told me they couldn't
> get into a section of the site because they only got a blank
> page. The page seems to be random, but I can easily reproduce
> the problem in my dev environment now.
>
> FYI,
>
> -Carl
>
> Bee Software LLC
> See us in action at: http://beethere.net/
>
> ----- Original Message ----
> From: Hartmaier Alexander <Alexander.Hartmaier@t-systems.at>
> To: embperl@perl.apache.org
> Sent: Monday, March 20, 2006 12:50:29 PM
> Subject: RE: Intermittent Segfaults
>
>
> I just found out that I have segfaults on my servers too.
> OS is debian testing
> The apache startup message should include all infos you might
> want to know too:
> [Mon Mar 20 18:27:05 2006] [notice] Apache/2.0.55 (Debian)
> Embperl/2.1.0 mod_ssl/2.0.55 OpenSSL/0.9.8a
> mod_apreq2-20051231/2.5.7 mod_perl/2.0.2 Perl/v5.8.8
> configured -- resuming normal operations
>
> I've recompiled Embperl today to make sure it uses the
> current software versions but that didn't help.
>
> -Alex
>
>
> -----Original Message-----
> From: Gerald Richter [mailto:richter@ecos.de]
> Sent: Friday, March 17, 2006 9:16 PM
> To: 'BeeThere Admin'; embperl@perl.apache.org
> Subject: RE: Intermittent Segfaults
>
>
> >
> > I have continued testing, and I can confidently say that the
> > problem is definitely not an out-of-memory issue.
>
> ok
>
> > The new dev
> > version you sent is segfaulting about once for every 100 page
> > requests in dev now, with no load except me clicking around,
> > on a machine with 2G total RAM and plenty of free memory.
> >
> > The segfaults have occurred during pretty much every type of
> > page request, and also not occurred on those same requests.
> > Hitting refresh will always result in the page being
> > correctly sent, with not segfault, on at most a couple pushes.
> >
> > Did you get the back-traces I sent?
>
> Yes. These backtraces are with the new version I sent, right?
> (I need to
> make sure the line numbers of the backtrace matches my source)
>
> > I sent them to your
> > personal account, but I realized that you may check the list
> > more. Every back-trace points to "EMBPERL2_Node_appendChild
> > .... at epdom.c:2835" as the point of segfaulting.
> >
> > The only Embperl tags I ever use are the PerlBlock '[* *], [+
> > +], [- -]' tags. Is there someway I can bypass this 'epdom'
> > code all together? (I don't see any reason for dom-parsing)
> >
>
> This code also parses [..] tags, so you will need it. (It
> never builds a
> full dom tree of your source, it only parses out the tags
> that you tell
> Embperl to process)
>
> I have to take a deeper look at the backtraces. I will come
> back to you as
> soon as possible
>
> Gerald
>
>
>
>
>
> ** Virus checked by BB-5000 Mailfilter **
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: embperl-unsubscribe@perl.apache.org
> For additional commands, e-mail: embperl-help@perl.apache.org
>
>
>
> *"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"
> *"*"*"*"*"*"*"*
> T-Systems Austria GesmbH
> Rennweg 97-99, 1030 Wien
> Telefon +43 (0)57057 0, Telefax +43 (0)57057 8155
> Bank Austria AG, BLZ 12000, Kto. 233-111-674/00, IBAN
> AT291200023311167400
> Handelsgericht Wien, FN 79340b DVR Nr. 0713520 ARA-Lizenz Nr. 12554
> ATU 15169001
>
> *"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"
> *"*"*"*"*"*"*"*
> Hinweis: Dieses E-mail kann vertrauliche und geschtzte
> Informationen enthalten.
> Sollten Sie nicht der beabsichtigte Empfnger sein,
> verstndigen Sie bitte den Absender und lschen Sie dieses
> E-mail dann sofort.
>
> Notice: This e-mail contains information that is confidential
> and may be privileged.
> If you are not the intended recipient, please notify the
> sender and then delete this e-mail immediately.
> *"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"
> *"*"*"*"*"*"*"*
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: embperl-unsubscribe@perl.apache.org
> For additional commands, e-mail: embperl-help@perl.apache.org
>
>
>
> ** Virus checked by BB-5000 Mailfilter **
> !DSPAM:4420651d76673852268083!
>



** Virus checked by BB-5000 Mailfilter **

---------------------------------------------------------------------
To unsubscribe, e-mail: embperl-unsubscribe@perl.apache.org
For additional commands, e-mail: embperl-help@perl.apache.org

FYI, I also got the same error, with the exact same epparse.c.reg file, trying to patch my 2.0.0 release.

Thanks,

-Carl


----- Original Message ----
From: Gerald Richter <richter@ecos.de>
To: BeeThere Admin <carl@beesw.com>; Hartmaier Alexander <Alexander.Hartmaier@t-systems.at>; embperl@perl.apache.org
Sent: Tuesday, March 21, 2006 11:53:38 PM
Subject: RE: Intermittent Segfaults


Hi,

Could you please give the attached patch a try and let me know if it fixes
the segfaults.

Gerald


---------------------------------------------------------------------------
Gerald Richter ecos electronic communication services gmbh
IT-Securitylösungen * Webapplikationen mit Apache/Perl/mod_perl/Embperl

Post: Tulpenstrasse 5 D-55276 Dienheim b. Mainz
E-Mail: richter@ecos.de Voice: +49 6133 939-122
WWW: http://www.ecos.de/ Fax: +49 6133 939-333
---------------------------------------------------------------------------
ECOS BB-5000 Firewall- und IT-Security Appliance: www.bb-5000.info
---------------------------------------------------------------------------



> -----Original Message-----
> From: BeeThere Admin [mailto:admin@beethere.net]
> Sent: Tuesday, March 21, 2006 12:38 AM
> To: Hartmaier Alexander; embperl@perl.apache.org
> Subject: Re: Intermittent Segfaults
>
> I don't know the details, it seems to be a pretty general
> problem. Gerald seems to be on it though. He even said that
> he was working through the weekend (bless his heart :-)
>
> The symptom on the user side, at least for me is a completely
> blank page. It looks like the server sends back a 200 OK, but
> then nothing else. There doesn't seem to be any way to debug
> the problem at the Embperl-user side because none of the page
> code ever gets executed, not even your base.epl (or whatever
> you call it). A page refresh will usually result in the
> expected page rendering, but at least for us, this is a
> critical issue holding a major release, business deals, etc.
>
> I looked into the logs because a user told me they couldn't
> get into a section of the site because they only got a blank
> page. The page seems to be random, but I can easily reproduce
> the problem in my dev environment now.
>
> FYI,
>
> -Carl
>
> Bee Software LLC
> See us in action at: http://beethere.net/
>
> ----- Original Message ----
> From: Hartmaier Alexander <Alexander.Hartmaier@t-systems.at>
> To: embperl@perl.apache.org
> Sent: Monday, March 20, 2006 12:50:29 PM
> Subject: RE: Intermittent Segfaults
>
>
> I just found out that I have segfaults on my servers too.
> OS is debian testing
> The apache startup message should include all infos you might
> want to know too:
> [Mon Mar 20 18:27:05 2006] [notice] Apache/2.0.55 (Debian)
> Embperl/2.1.0 mod_ssl/2.0.55 OpenSSL/0.9.8a
> mod_apreq2-20051231/2.5.7 mod_perl/2.0.2 Perl/v5.8.8
> configured -- resuming normal operations
>
> I've recompiled Embperl today to make sure it uses the
> current software versions but that didn't help.
>
> -Alex
>
>
> -----Original Message-----
> From: Gerald Richter [mailto:richter@ecos.de]
> Sent: Friday, March 17, 2006 9:16 PM
> To: 'BeeThere Admin'; embperl@perl.apache.org
> Subject: RE: Intermittent Segfaults
>
>
> >
> > I have continued testing, and I can confidently say that the
> > problem is definitely not an out-of-memory issue.
>
> ok
>
> > The new dev
> > version you sent is segfaulting about once for every 100 page
> > requests in dev now, with no load except me clicking around,
> > on a machine with 2G total RAM and plenty of free memory.
> >
> > The segfaults have occurred during pretty much every type of
> > page request, and also not occurred on those same requests.
> > Hitting refresh will always result in the page being
> > correctly sent, with not segfault, on at most a couple pushes.
> >
> > Did you get the back-traces I sent?
>
> Yes. These backtraces are with the new version I sent, right?
> (I need to
> make sure the line numbers of the backtrace matches my source)
>
> > I sent them to your
> > personal account, but I realized that you may check the list
> > more. Every back-trace points to "EMBPERL2_Node_appendChild
> > .... at epdom.c:2835" as the point of segfaulting.
> >
> > The only Embperl tags I ever use are the PerlBlock '[* *], [+
> > +], [- -]' tags. Is there someway I can bypass this 'epdom'
> > code all together? (I don't see any reason for dom-parsing)
> >
>
> This code also parses [..] tags, so you will need it. (It
> never builds a
> full dom tree of your source, it only parses out the tags
> that you tell
> Embperl to process)
>
> I have to take a deeper look at the backtraces. I will come
> back to you as
> soon as possible
>
> Gerald
>
>
>
>
>
> ** Virus checked by BB-5000 Mailfilter **
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: embperl-unsubscribe@perl.apache.org
> For additional commands, e-mail: embperl-help@perl.apache.org
>
>
>
> *"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"
> *"*"*"*"*"*"*"*
> T-Systems Austria GesmbH
> Rennweg 97-99, 1030 Wien
> Telefon +43 (0)57057 0, Telefax +43 (0)57057 8155
> Bank Austria AG, BLZ 12000, Kto. 233-111-674/00, IBAN
> AT291200023311167400
> Handelsgericht Wien, FN 79340b DVR Nr. 0713520 ARA-Lizenz Nr. 12554
> ATU 15169001
>
> *"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"
> *"*"*"*"*"*"*"*
> Hinweis: Dieses E-mail kann vertrauliche und geschtzte
> Informationen enthalten.
> Sollten Sie nicht der beabsichtigte Empfnger sein,
> verstndigen Sie bitte den Absender und lschen Sie dieses
> E-mail dann sofort.
>
> Notice: This e-mail contains information that is confidential
> and may be privileged.
> If you are not the intended recipient, please notify the
> sender and then delete this e-mail immediately.
> *"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"
> *"*"*"*"*"*"*"*
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: embperl-unsubscribe@perl.apache.org
> For additional commands, e-mail: embperl-help@perl.apache.org
>
>
>
> ** Virus checked by BB-5000 Mailfilter **
> !DSPAM:4420651d76673852268083!
>



** Virus checked by BB-5000 Mailfilter **

---------------------------------------------------------------------
To unsubscribe, e-mail: embperl-unsubscribe@perl.apache.org
For additional commands, e-mail: embperl-help@perl.apache.org