>
> I saw yesterday that you released Embperl 2.2.0 and use it since then.
> Today I discovered that the segfaults are back ;-( Did you
> include the patch which should become 2.1.1 in 2.2.0?
>
Yes, the fix is in 2.2.0.
If I remember right, I send you an patched Embperl ver
I saw yesterday that you released Embperl 2.2.0 and use it since then.
Today I discovered that the segfaults are back ;-(
Did you include the patch which should become 2.1.1 in 2.2.0?
-Alex
> -Original Message-
> From: Gerald Richter [mailto:[EMAIL PROTECTED]
> Sent: Wednesday,
>
> I figured out that I have to type 'c' to make apache continue.
Yes, sorry I forgot to mention this
> Just a few minutes ago it segfaulted again:
>
> (gdb) c
> Continuing.
>
> Program received signal SIGPIPE, Broken pipe.
No, this is no Segfault, this is the PIPE signal, this happen when s
Alexander [mailto:[EMAIL PROTECTED]
Sent: Tuesday, April 11, 2006 2:40 PM
To: embperl@perl.apache.org
Subject: RE: Fixed! Re: Intermittent Segfaults
As soon as I attach gdb to the apache2 process the embperl page stops working.
When I detach gdb it gets working again.
Never used gdb before, maybe
ginal Message-
From: Gerald Richter [mailto:[EMAIL PROTECTED]
Sent: Friday, April 07, 2006 9:01 PM
To: Hartmaier Alexander; embperl@perl.apache.org
Subject: RE: Fixed! Re: Intermittent Segfaults
> >
> > I have compiled and installed with the debug switch, how do
> i get the
>
> >
> > I have compiled and installed with the debug switch, how do
> i get the
> > stack backtrace now?
> >
>
The easiest is to start httpd with the -X option, then it
will only start one process, then you attach with gdb to
process (like gdb /path/to/httpd ), do the
request and when you g
smime.p7m
Description: S/MIME encrypted message
: Intermittent Segfaults
>
> I installed 2.1.1_dev you sent me and the segfaults still occur:
> [Thu Apr 06 10:00:35 2006] [notice] child pid 13980 exit
> signal Segmentation fault (11) [Thu Apr 06 10:00:49 2006]
> [notice] child pid 12531 exit signal Segmentation fault (11)
> [Thu Apr 06 10:5
>
> I installed 2.1.1_dev you sent me and the segfaults still occur:
> [Thu Apr 06 10:00:35 2006] [notice] child pid 13980 exit
> signal Segmentation fault (11) [Thu Apr 06 10:00:49 2006]
> [notice] child pid 12531 exit signal Segmentation fault (11)
> [Thu Apr 06 10:58:12 20
I installed 2.1.1_dev you sent me and the segfaults still occur:
[Thu Apr 06 10:00:35 2006] [notice] child pid 13980 exit signal Segmentation
fault (11)
[Thu Apr 06 10:00:49 2006] [notice] child pid 12531 exit signal Segmentation
fault (11)
[Thu Apr 06 10:58:12 2006] [notice] child pid 28154
It seems I can't reach the list at the moment.
Yesterday I twice attempted to send a problem report that is now at
http://a2e.de/phm/adv/embperl/
but didn't get it mailed back to me from the list.
-
To unsubscribe, e-ma
ll become 2.1.1...
>
Yes
Gerald
> -Alex
>
>
> -Original Message-
> From: Gerald Richter [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, March 22, 2006 9:01 PM
> To: 'BeeThere Admin'; Hartmaier Alexander; embperl@perl.apache.org
> Subject: RE: Fixed! Re: Int
ubject: RE: Fixed! Re: Intermittent Segfaults
>
> Yes! The new release went through all of my torture tests,
> with no segfaults, and an unexpected ~15% speedup in
> performance over my 2.0.0 release, with compiler debugging flags on!
>
Great news :-)
I will release this soo
>
> Yes! The new release went through all of my torture tests,
> with no segfaults, and an unexpected ~15% speedup in
> performance over my 2.0.0 release, with compiler debugging flags on!
>
Great news :-)
I will release this soon as new version.
Gerald
** Virus che
Yes! The new release went through all of my torture tests, with no segfaults,
and an unexpected ~15% speedup in performance over my 2.0.0 release, with
compiler debugging flags on!
-Carl
-
To unsubscribe, e-mail: [EMAIL
CTED]>; 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 Richt
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
Hi,
Could you please give the attached patch a try and let me know if it fixes
the segfaults.
Gerald
---
Gerald Richterecos electronic communication services gmbh
IT-Securitylösungen * Webapplikationen mit
ment now.
FYI,
-Carl
Bee Software LLC
See us in action at: http://beethere.net/
- Original Message
From: Hartmaier Alexander <[EMAIL PROTECTED]>
To: embperl@perl.apache.org
Sent: Monday, March 20, 2006 12:50:29 PM
Subject: RE: Intermittent Segfaults
I just found out that I
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
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
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 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 developm
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.
It is not based on any particular or even area of my site URL. It
On Wednesday 28 April 2004 06:51 pm, Gerald Richter wrote:
> Beau E. Cox wrote:
> > Gerald -
> >
> > Have you received my emails detailing my segfault problem?
>
> Yes, but I was out of office yesterday the whole and today I will also
> visit a customer for most of the day, so I guess I will not fi
On Wednesday 28 April 2004 06:51 pm, Gerald Richter wrote:
> Beau E. Cox wrote:
> > Gerald -
> >
> > Have you received my emails detailing my segfault problem?
>
> Yes, but I was out of office yesterday the whole and today I will also
> visit a customer for most of the day, so I guess I will not fi
Beau E. Cox wrote:
> Gerald -
>
> Have you received my emails detailing my segfault problem?
>
Yes, but I was out of office yesterday the whole and today I will also visit
a customer for most of the day, so I guess I will not find time before
tomorrow to look deeper into your problems. Sorry!
Gera
Gerald -
Have you received my emails detailing my segfault problem?
Aloha => Beau;
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Gerald -
More on my production-only segfault...
I put the following code into eputil.c (the Embperl routine
closest to the segfault):
--- /home/install/httpd/2.1-db/src/embperl/embperl/eputil.c 2004-03-07
09:44:14.0 -1000
+++ ../embperl/eputil.c 2004-04-28 05:43:01.118170288 -1000
@
On Monday 26 April 2004 06:04 pm, Gerald Richter wrote:
> > Program received signal SIGSEGV, Segmentation fault.
> > [Switching to Thread 16384 (LWP 5447)]
> > 0x40575711 in S_hv_fetch_common (my_perl=0x84bc198, hv=0x88dade8,
>
> keysv=0x0,
>
> > key=0x4070dbc6 "EMBPERL_ALLOW", klen=13, flags=0
On Monday 26 April 2004 06:04 pm, Gerald Richter wrote:
> > Program received signal SIGSEGV, Segmentation fault.
> > [Switching to Thread 16384 (LWP 5447)]
> > 0x40575711 in S_hv_fetch_common (my_perl=0x84bc198, hv=0x88dade8,
>
> keysv=0x0,
>
> > key=0x4070dbc6 "EMBPERL_ALLOW", klen=13, flags=0
>
> Program received signal SIGSEGV, Segmentation fault.
> [Switching to Thread 16384 (LWP 5447)]
> 0x40575711 in S_hv_fetch_common (my_perl=0x84bc198, hv=0x88dade8,
keysv=0x0,
> key=0x4070dbc6 "EMBPERL_ALLOW", klen=13, flags=0, action=8, val=0x0,
> hash=138139023)
> at hv.c:631
> 631
Hi Gerald -
My segfaults happen in production even with perl back to
5.8.3. I must be a configuration problem. Here is what
I' getting:
-8<-- Start Bug Report 8<--
1. Problem Description:
segfaults on embperl pages. Content is transf
ibraries used by production and test will be
for sure the same, right?)
dropped back to Apache 2.0 cvs (from 2.1)
dropped back from Embperl cvs to latest beta
Results are the same: test soild, production segfaults.
I'll drop back to perl 5.8.3 and rebuild everthing (again)
tonight. If th
Perrin Harkins wrote:
> On Fri, 2004-04-23 at 18:21, Beau E. Cox wrote:
>> 1) are core dumps automatically generated by seqfaults? If not,
>> how do I have Apache generate them?
>
> Sounds like you're looking for this:
>
http://perl.apache.org/docs/2.0/user/help/help.html#Resolving_Segmentation_Fau
On Fri, 2004-04-23 at 18:21, Beau E. Cox wrote:
> 1) are core dumps automatically generated by seqfaults? If not,
> how do I have Apache generate them?
Sounds like you're looking for this:
http://perl.apache.org/docs/2.0/user/help/help.html#Resolving_Segmentation_Faults
- Perrin
---
output is properly received
by the browser) of requests to Embperl pages (not the first
request to a page and then randomly after that). I constructed
a simple simple page for testing that segfaults:
Embperl test
Embperl test
2 + 2 = [+ 4 +].
I have re-installed EVERYTHING on both servers
925152
-
- Original Message -
From: "Robert Norris" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, May 10, 2002 1:42 AM
Subject: Apache
t.epl:
---
[- print OUT "foo" -]
---
the httpd handling the request segfaults. gdb gives the following
backtrace:
---
#0 0x40208660 in embperl_String2AV () from
/usr/local/lib/perl/5.6.1/auto/Embperl/Embperl.so
#1 0x4020a665 in embperl_GetApacheAppConfig () from
/usr/local/lib/
Hi,
sorry for the later answer, but this week is a really busy one for me...
>
> We just recently upgraded to 1.3.4 and are suddenly getting random
> segfaults and bus errors.
>
> Server: Stronghold/2.4.2 Apache/1.3.6 C2NetEU/2412 (Unix) mod_perl/1.25
> perl5 (5.0 patchle
Howdy,
We just recently upgraded to 1.3.4 and are suddenly getting random
segfaults and bus errors.
Server: Stronghold/2.4.2 Apache/1.3.6 C2NetEU/2412 (Unix) mod_perl/1.25
perl5 (5.0 patchlevel 5 subversion 3)
Here is the backtrace of one of the core files, all of the ones we've
collected
> When I call Embperl::Execute() instead of just Execute() it segfaults. I
need
> this, because I was trying to call this from a module that I 'require' in
> base.epl. But even when I do this in base.epl itself Execute() works, but
> Embperl::Execute() segfaults!?
>
When I call Embperl::Execute() instead of just Execute() it segfaults. I need
this, because I was trying to call this from a module that I 'require' in
base.epl. But even when I do this in base.epl itself Execute() works, but
Embperl::Execute() segfaults!?
Jochen
--
Jochen To
43 matches
Mail list logo
