Re: POST large amount of data causes segmentation fault

ussell Lundberg mailto:lundberg.russ...@gmail.com> > Betreff: Re: POST large amount of data causes segmentation fault Datum: 09.02.2020, 19:22 Uhr An: Scott Alexander mailto:scott.alexan...@humak.fi> > CC: modperl@perl.apache.org mailto:modperl@perl.apache.org> > You might want t

Re: POST large amount of data causes segmentation fault

On Sun, Feb 09, 2020 at 04:26:31PM +0100, Vincent Veyron wrote: > On Sun, 9 Feb 2020 10:57:04 + > Scott Alexander wrote: > > > I meant I'm posting data from a form, javascript is collecting a series of > > numbers from a as a string. > > Not really clear what happens here? I guess

Re: POST large amount of data causes segmentation fault

On 09.02.2020 16:26, Vincent Veyron wrote: On Sun, 9 Feb 2020 10:57:04 + Scott Alexander wrote: I meant I'm posting data from a form, javascript is collecting a series of numbers from a as a string. Not really clear what happens here? I guess Javascript writes the content of the text

Re: POST large amount of data causes segmentation fault

On Sun, 9 Feb 2020 10:57:04 + Scott Alexander wrote: > I meant I'm posting data from a form, javascript is collecting a series of > numbers from a as a string. Not really clear what happens here? I guess Javascript writes the content of the text input? > Javascript seperates each number

Re: POST large amount of data causes segmentation fault

..@humak.fi > > -- > *From:* Russell Lundberg > *Sent:* 09 February 2020 12:12 > *To:* Scott Alexander > *Cc:* modperl@perl.apache.org > *Subject:* Re: POST large amount of data causes segmentation fault > > Scott, > > Are you say

Re: POST large amount of data causes segmentation fault

@humak.fi> From: Russell Lundberg Sent: 09 February 2020 12:12 To: Scott Alexander Cc: modperl@perl.apache.org Subject: Re: POST large amount of data causes segmentation fault Scott, Are you saying that the incoming request has a length of 42,000+ characters? Apa

Re: POST large amount of data causes segmentation fault

Scott, Are you saying that the incoming request has a length of 42,000+ characters? Apache docs say 8,192 characters is the maximum length of a URL. Would it be possible to reduce the length of the request until the segmentation fault stops occurring? -- Russell Lundberg Latest Blog Post

Random segmentation fault

pid 19350:tid 140212941145984] AH00052: child pid 1487 exit signal Segmentation fault (11) [Tue Jan 12 14:32:25.852857 2016] [core:notice] [pid 19350:tid 140212941145984] AH00052: child pid 1488 exit signal Aborted (6) Out of memory! Out of memory! PerlIOApache_flush: flush can't be called before the response

Re: Random segmentation fault

ete system > are using less than 15% of ram ... > > *** Error in `/usr/sbin/apache2': double free or corruption (!prev): > 0x7f859f10 *** > [Tue Jan 12 14:32:25.852805 2016] [core:notice] [pid 19350:tid > 140212941145984] AH00052: child pid 1487 exit signal Segmentation faul

Re: Random segmentation fault

Steve, John: I did a bisect today against perl git, using mod_perl 2.0.9 and apache 2.2.29 to find out where my two issues were caused. It turns out that both of my problems, which were: - panic: attempt to copy freed scalar to and also - segmentation fault caused by a specific

Re: Random segmentation fault

my two issues were caused. It turns out that > both of my problems, which were: > > - panic: attempt to copy freed scalar to > > and also > > - segmentation fault caused by a specific "return" statement > > Are *BOTH* caused by the following commit

Re: Random segmentation fault

I'll probably deal with this by staying on Debian 7 for the near future. I'll attempt upgrading again in Debian 9. On Mon, Sep 14, 2015 at 10:27 AM, Michael Schout wrote: > On 9/11/15 2:26 PM, John Dunlap wrote: > > I found a lot of stuff like the following in my Apache logs.

Re: Random segmentation fault

On 9/11/15 2:26 PM, John Dunlap wrote: > I found a lot of stuff like the following in my Apache logs. Is it > possible to get this kind of output from Apache when the server runs > out of memory? I wouldn't have expected so. It has all the hallmarks > of something more sinister. For whatever its

Re: Random segmentation fault

No, I have not. I don't have time to mess with compiling my own version and I certainly don't have time to support a custom version. I always run the version that comes with Debian out of the box. On Mon, Sep 14, 2015 at 1:12 PM, Steve Hay wrote: > Have you tried

Re: Random segmentation fault

Have you tried 5.20.3? This has just been released and contains a number of crash fixes. (I wonder if #123398 might be relevant?) On 14 September 2015 at 15:57, John Dunlap wrote: > I'll probably deal with this by staying on Debian 7 for the near future. > I'll attempt upgrading

Re: Random segmentation fault

On 9/14/15 12:12 PM, Steve Hay wrote: > Have you tried 5.20.3? This has just been released and contains a > number of crash fixes. (I wonder if #123398 might be relevant?) I just tried 5.20.3. For my issue (mentioned earlier in this thread), 5.20.3 does not help. I'll post a followup message in

Re: Random segmentation fault

d pid 2088 exit signal Segmentation fault (11) [Thu Sep 03 21:13:03.406215 2015] [core:notice] [pid 13199:tid 140364918835072] AH00052: child pid 2121 exit signal Segmentation fault (11) [Thu Sep 03 21:13:05.417909 2015] [core:notice] [pid 13199:tid 140364918835072] AH00052: child pid 2165 e

Random segmentation fault

s it. I've been sifting through the server logs looking for problems and I'm seeing a lot of errors similar to the following: [Thu Sep 03 21:12:52.382357 2015] [core:notice] [pid 13199:tid 140364918835072] AH00052: child pid 2088 exit signal Segmentation fault (11) [Thu Sep 03 21:13:03.406215 2015] [c

Re: mod_perl Segmentation fault with ModProxyHtml

am using httpd 2.2.15(worker MPM), perl 5.20.1 with modperl 2.0.8 to use ProxyPerlHtml-3.6 as an OutputFilter for substitution.When I try to test my system using apache benchmark and when the concurrency(-c) option is high, I receive a Segmentation fault which seems to be a memory problem. I used

mod_perl Segmentation fault with ModProxyHtml

Hello, I am using httpd 2.2.15(worker MPM), perl 5.20.1 with modperl 2.0.8 to use ProxyPerlHtml-3.6 as an OutputFilter for substitution.When I try to test my system using apache benchmark and when the concurrency(-c) option is high, I receive a Segmentation fault which seems to be a memory

Segmentation fault when starting Apache 2.2.26 with Perl 5.18.1 and mod_perl 2.0.8

: line 78: 28245 Segmentation fault $HTTPD -k $ARGV dmesg contains this message: httpd[28245]: segfault at c ip b702020b sp bf84a000 error 4 in mod_perl.so[b7001000+37000] Here are the details of my configuration: root@nas:~# perl -V Summary of my perl5 (revision 5 version 18 subversion 1

Debugging segmentation fault

I run a busy website algebra.com on a CentOS server. Occasionally, apache processes crash with a segmentation fault. I often get 140+ object requests per second, so isolating which request caused segfault, by looking at logs, is not practicable. I want to know if I can at least isolate

Re: Debugging segmentation fault

On Mon, Sep 2, 2013 at 1:12 PM, Igor Chudov ichu...@gmail.com wrote: I run a busy website algebra.com on a CentOS server. Occasionally, apache processes crash with a segmentation fault. I often get 140+ object requests per second, so isolating which request caused segfault, by looking

Re: Segmentation fault on form posting

I also encounter this problem occasionally. So your post is quite familiar. If the first thing you do is print the parameters, what's the second thing? Form posts almost always trigger external processes, databases, mail servers, etc. The external process is more likely to be causing the

Re: Segmentation fault on form posting

Here's the code I mentioned in my last post. It's included in my distro NoSQL::PL2SQL #include EXTERN.h #include perl.h #include XSUB.h #include ppport.h SV* typeis ( SV* what ) ; SV* typeis ( SV* what ) { if ( SvIOK( what ) ) return newSVpvs( integer ) ; else

RE: [mp2] mod_perl 2.0.7 Segmentation fault in OutputFilter(?)

I'm not a modperl expert, but I do know that modperl does some unusual things with threads and memory, to try to make separate threads act more like separate processes, i.e., to treat separate threads as though they had separate memory spaces. However, I think it may depend on which [...]

[mp2] mod_perl 2.0.7 Segmentation fault in OutputFilter(?)

Hi, I am using httpd 2.2.23 (worker MPM), perl 5.14.2, mod-perl-2.0.7 on a 64bit-CentOS-6.3 system and received every 2-4 hours a Segmentation fault (maybe from the output filter). :-( My apache config looks like: Directory /www/xxx/htdocs/   Order Allow,Deny   Allow from all   RewriteEngine

Re: [mp2] mod_perl 2.0.7 Segmentation fault in OutputFilter(?)

you use, and I don't know what are the rules for worker MPM. With that backdrop, given that the segmentation fault is happening every 2-4 hours, from a general debugging perspective I would suspect that: (a) some resource is somehow being exhausted; or (b) something is getting corrupted because

Re: apache2 + mod_perl + Catalyst + Session = Segmentation fault

On Sat, Sep 29, 2012 at 1:08 PM, Stefan Profanter catal...@s.profanter.me wrote: Looks like you are using Storable to stream out cookies? Looks like something in there is causing Storable to puke. I see things like array_call, store_blessed, store_hash... So I'm guessing your passing

Re: apache2 + mod_perl + Catalyst + Session = Segmentation fault

On 13 November 2012 15:23, Ævar Arnfjörð Bjarmason ava...@gmail.com wrote: On Sat, Sep 29, 2012 at 1:08 PM, Stefan Profanter catal...@s.profanter.me wrote: Looks like you are using Storable to stream out cookies? Looks like something in there is causing Storable to puke. I see things

Re: apache2 + mod_perl + Catalyst + Session = Segmentation fault

On Tue, Nov 13, 2012 at 3:48 PM, demerphq demer...@gmail.com wrote: On 13 November 2012 15:23, Ævar Arnfjörð Bjarmason ava...@gmail.com wrote: On Sat, Sep 29, 2012 at 1:08 PM, Stefan Profanter catal...@s.profanter.me wrote: Looks like you are using Storable to stream out cookies? Looks

AW: apache2 + mod_perl + Catalyst + Session = Segmentation fault

Looks like you are using Storable to stream out cookies? Looks like something in there is causing Storable to puke. I see things like array_call, store_blessed, store_hash... So I'm guessing your passing Storable some kind of object? Does it have any recursive parts? I googled

Re: apache2 + mod_perl + Catalyst + Session = Segmentation fault

everything works fine. But after login, only the first page opens, each second try to open another page results in a Segmentation Fault. Even pages which don’t require login. If I then disable or delete the Cookies, the Site works again. So my guess is that there is somewhere a problem with Session

Re: apache2 + mod_perl + Catalyst + Session = Segmentation fault

(also with same Session Plugins). The first time, I access the site everything works fine. But after login, only the first page opens, each second try to open another page results in a Segmentation Fault. Even pages which don’t require login. If I then disable or delete the Cookies, the Site

Re: apache2 + mod_perl + Catalyst + Session = Segmentation fault

On Fri, Sep 28, 2012 at 12:33 PM, demerphq demer...@gmail.com wrote: Maybe look at Sereal as an alternative to Storable. https://github.com/Sereal/Sereal/ http://search.cpan.org/~smueller/Sereal-Decoder/lib/Sereal/Decoder.pm

Re: mod_perl causing Apache Segmentation fault

Hi Dave, Thanks for this pointer. Got it fixed in the end by changing a part of my Apache configuration from PerlSwitches -I/srv/www/example.com/application/lib/ Perl use lib qw( /srv/www/example.com/application/lib/ ); /Perl PerlModule application to Perl use lib qw(

Re: mod_perl causing Apache Segmentation fault

So duplicating a path in -I and use lib casues a dump? Smells like a bug to me. On 20 Feb 2012, at 14:25, Mauritz Hansen wrote: Hi Dave, Thanks for this pointer. Got it fixed in the end by changing a part of my Apache configuration from PerlSwitches

mod_perl causing Apache Segmentation fault

NOTE: I posted have posted this question on Stackoverflow and have not yet received an answer. * My mod_perl appears to cause a segmentation fault in my Apache. 'httpd -X' simply gives 'Segmentation Fault' and my server does not start. I am using

Re: mod_perl causing Apache Segmentation fault

On 17 Feb 2012, at 14:03, Mauritz Hansen wrote: #17 0x0046432b in invoke_cmd (cmd=0x5b9880, parms=0x7fffe770, mconfig=0x844728, args=0x89b7d8 use lib qw( /usr/local/apache2/virtualhosts/api.nwwi.nl /httpdocs/lib/ );\n) at config.c:757 This appears to be what it's trying to

Re: mod_perl causing Apache Segmentation fault

to the earlier DateTime, which worked for him. It may be totally unrelated to your problem, but I had many varying symptoms depending on configuration etc, and some of the errors gave no hint as to the problem being in Classify.dll. HTH :) My mod_perl appears to cause a segmentation fault in my Apache

Re: [SOLVED] Re: How to run shell command from response handler? (Apache2 child segmentation fault)

; was causing the segmentation fault after several successful requests, even though no functions whatsoever were called. Since this appears to be a bug in Test::MockObject, I reported the bug here: https://rt.cpan.org/Public/Bug

Re: [SOLVED] Re: How to run shell command from response handler? (Apache2 child segmentation fault)

; was causing the segmentation fault after several successful requests, even though no functions whatsoever were called. Since this appears to be a bug in Test::MockObject, I reported the bug here: https://rt.cpan.org/Public/Bug/Display.html?id=73723 The bug report shows the exact minimal handler

How to run shell command from response handler? (Apache2 child segmentation fault)

I am trying to run a shell command from a mod_perl2 response handler. It works properly for some number of HTTP requests, but sometimes it fails (somewhat randomly) and I see in my Apache2 error log that one of the Apache2 child processes has died with a segmentation fault. For example, /var/log

Re: How to run shell command from response handler? (Apache2 child segmentation fault)

has died with a segmentation fault. For example, /var/log/apache2/error.log shows: [Tue Jan 03 12:16:10 2012] [notice] child pid 3538 exit signal Segmentation fault (11) Is this normal?  How does one normally run a shell command from a response handler?  I do not want to return the command's

Re: How to run shell command from response handler? (Apache2 child segmentation fault)

processes has died with a segmentation fault. For example, /var/log/apache2/error.log shows: [Tue Jan 03 12:16:10 2012] [notice] child pid 3538 exit signal Segmentation fault (11) Is this normal? How does one normally run a shell command from a response handler? I do not want to return

Re: How to run shell command from response handler? (Apache2 child segmentation fault)

a shell command from a mod_perl2 response handler. It works properly for some number of HTTP requests, but sometimes it fails (somewhat randomly) and I see in my Apache2 error log that one of the Apache2 child processes has died with a segmentation fault. For example, /var/log/apache2

[SOLVED] Re: How to run shell command from response handler? (Apache2 child segmentation fault)

Thanks for the suggestion. I tried it with prefork and the problem still occurred. HOWEVER, I then decided to remove all modules down to a minimal example, and discovered that the mere inclusion of the following module: use Test::MockObject; was causing the segmentation fault after several

Re: A lot of segmentation fault, Ubuntu Hardy, apache with mod_perl

Igor Chudov wrote: On Sun, Aug 9, 2009 at 7:08 AM, Nick Wellnhofer wellnho...@aevum.de mailto:wellnho...@aevum.de wrote: Igor Chudov wrote: In the logs, I see a lot of error messages saying: segmentation fault Are you using the worker MPM? If yes, try the prefork MPM

Re: A lot of segmentation fault, Ubuntu Hardy, apache with mod_perl

On Sun, Aug 9, 2009 at 7:08 AM, Nick Wellnhofer wellnho...@aevum.de wrote: Igor Chudov wrote: In the logs, I see a lot of error messages saying: segmentation fault Are you using the worker MPM? If yes, try the prefork MPM instead. Nick, thank you, per your advice, I did try using prefork

A lot of segmentation fault, Ubuntu Hardy, apache with mod_perl

I just moved my website algebra.com, from my old trusty Fedora 3 server, to my brand new Ubuntu Hardy server. The Hardy server is fully patched. In the logs, I see a lot of error messages saying segmentation fault in the error.log file. No other details like pids, etc are provided. ~==apache2

Re: Segmentation fault with Perl-Catalyst app

Perrin Harkins wrote: On Sun, Dec 7, 2008 at 12:51 PM, Terence Monteiro tere...@deeproot.co.in wrote: I'm getting segmentation faults with apache child processes. I'm running a Catalyst application using DBIx::SearchBuilder in the backend to accesss a mysql database. My guess is that

Segmentation fault with Perl-Catalyst app

Hi, I'm getting segmentation faults with apache child processes. I'm running a Catalyst application using DBIx::SearchBuilder in the backend to accesss a mysql database. I'm running this on a debian quad core CPU server with 4 gigs RAM. I enabled core dumping and got a gdb backtrace as follows:

Re: Segmentation fault with Perl-Catalyst app

Terence Monteiro wrote: Hi, I'm getting segmentation faults with apache child processes. I'm running a Catalyst application using DBIx::SearchBuilder in the backend to accesss a mysql database. I'm running this on a debian quad core CPU server with 4 gigs RAM. I enabled core dumping and got

Re: Segmentation fault with Perl-Catalyst app

Terence Monteiro wrote: Terence Monteiro wrote: Hi, I'm getting segmentation faults with apache child processes. I'm running a Catalyst application using DBIx::SearchBuilder in the backend to accesss a mysql database. I'm running this on a debian quad core CPU server with 4 gigs RAM. I

Re: Segmentation fault with Perl-Catalyst app

Terence Monteiro wrote: [...] Hi. I cannot help you, but if you want help quickly, it helps if you provide some additional information, like : - which platform (Windows, Unix, Linux, version ?) - which version of Apache, and from where it comes - which version of mod_perl, and from where it

Re: Segmentation fault with Perl-Catalyst app

On Sun, Dec 7, 2008 at 12:51 PM, Terence Monteiro [EMAIL PROTECTED] wrote: I'm getting segmentation faults with apache child processes. I'm running a Catalyst application using DBIx::SearchBuilder in the backend to accesss a mysql database. My guess is that you're opening database handles in

Re: Segmentation fault with Perl-Catalyst app

André Warnier wrote: Terence Monteiro wrote: [...] Hi. I cannot help you, but if you want help quickly, it helps if you provide some additional information, like : - which platform (Windows, Unix, Linux, version ?) - which version of Apache, and from where it comes - which version of

Re: Re: Re: Re: Process exists - Segmentation fault

@perl.apache.org Subject: Re: Re: Re: Process exists - Segmentation fault Hi Its me again, But still the things are not working right. I tried to recompile Embperl and put PerlModule Embperl after LoadModule embperl_module .. Now i do not remember it was before or now

Re: Re: Re: Re: Process exists - Segmentation fault

: Re: Process exists - Segmentation fault Hi Its me again, But still the things are not working right. I tried to recompile Embperl and put PerlModule Embperl after LoadModule embperl_module .. Now i do not remember it was before or now but after i uncomment the 'PerlModule

RE: Re: Re: Re: Process exists - Segmentation fault

Subject: Re: Re: Re: Process exists - Segmentation fault Hi Its me again, But still the things are not working right. I tried to recompile Embperl and put PerlModule Embperl after LoadModule embperl_module .. Now i do not remember it was before or now but after i uncomment

Re: Re: Re: Process exists - Segmentation fault

Segmentation fault (11) (May be error and page refreshes itself i mean the code produces output.) and page appears , sometimes the same error appears twice and page does not appears. I am not sure have this error been encountered by someone else but things are not working right for me . Also

Re: Process exists - Segmentation fault

Gerald -Original Message- From: abhishek jain [mailto:[EMAIL PROTECTED] Sent: Thursday, January 03, 2008 4:59 AM To: modperl@perl.apache.org Subject: Process exists - Segmentation fault Hi, I am running modperl 2.x + embperl on centos 4.5 Now when i run

RE: Re: Process exists - Segmentation fault

Please add a PerlModule Embperl Somewhere _after_ the LoadModule Gerald -Original Message- From: abhishek jain [mailto:[EMAIL PROTECTED] Sent: Thursday, January 03, 2008 12:53 PM To: Gerald Richter Cc: modperl@perl.apache.org Subject: Re: Process exists - Segmentation fault

Re: Re: Process exists - Segmentation fault

Richter Cc: modperl@perl.apache.org Subject: Re: Process exists - Segmentation fault Hi, I have the following statement in my httpd.conf LoadModule embperl_module /usr/lib/perl5/site_perl/5.8.8/i386-linux-thread-multi/auto/Em bperl/Embperl.so I do not have a related PerlModule

RE: Re: Re: Process exists - Segmentation fault

: abhishek jain [mailto:[EMAIL PROTECTED] Sent: Thursday, January 03, 2008 8:20 PM To: Gerald Richter Cc: modperl@perl.apache.org Subject: Re: Re: Process exists - Segmentation fault Hi, Adding PerlModule Embperl did not solved the problem , infact it aggreviated it. With this the page

Re: Process exists - Segmentation fault

for Embperl in your httpd.conf Really? Any ides what about that triggers a segmentation fault ? -- Philippe M. Chiasson GPG: F9BFE0C2480E7680 1AE53631CB32A107 88C3A5A5 http://gozer.ectoplasm.org/ m/gozer\@(apache|cpan|ectoplasm)\.org/ signature.asc Description: OpenPGP digital signature

Unqualified segmentation fault from Apache2::Request-new()

22461 exit signal Segmentation fault (11) ### End Log Colin

Re: Unqualified segmentation fault from Apache2::Request-new()

Colin Wetherbee wrote: use Apache2::RequestRec; use Apache2::Const -compile = qw(OK); To be clear, this also occurs with 'use Apache2::Request' at the top. :) Colin

Re: [mp1] PerlFreshRestart, perl_reload_inc, segmentation fault (patch)

Michael Rendell wrote: Subject: [mp1] PerlFreshRestart, perl_reload_inc, segmentation fault (patch) When using mod_perl-1.30 (with perl 5.8.5, apache 1.3.37) with PerlFreshRestart On (yes, dangerous), httpd gets a segmentation fault. Yup, verified this one. Using valgrind, discovered

Re: segmentation fault.

that an apache child died because of a segmentation fault I believe here is the error or I guess notice message. [notice] child pid 25946 exit signal Segmentation fault (11) # ? do I have to worry about this notice ? what we are building will be a live system. The best way to get an understanding

Re: segmentation fault.

Tyler Bird wrote: Clinton Gormley wrote: On Wed, 2007-05-23 at 17:04 -0400, Dondi M. Stroma wrote: I've also gotten segfaults from reading a bad cookie. Another segfault problem I experienced was caused by using a lexical variable in a sub in a Registry script that was declared outside of

Re: segmentation fault.

, but in my logs I see that an apache child died because of a segmentation fault I believe here is the error or I guess notice message. [notice] child pid 25946 exit signal Segmentation fault (11) # ? do I have to worry about this notice ? what we are building will be a live system. The best

segmentation fault.

of a segmentation fault I believe here is the error or I guess notice message. [notice] child pid 25946 exit signal Segmentation fault (11) # ? do I have to worry about this notice ? what we are building will be a live system. My question is why is it doing this? I have but try{} catch

Re: segmentation fault.

. We recently upgraded to mod_perl 2.0 and apache 2.2 on RHL5 I am having a problem. When I refresh a certain page 5 times or about ( it's completely random ) The page renders fine, but in my logs I see that an apache child died because of a segmentation fault I believe here is the error

Re: segmentation fault.

to 20 percent of the time. - Original Message - From: Jonathan Vanasco [EMAIL PROTECTED] To: modperl mod_perl modperl@perl.apache.org Sent: Wednesday, May 23, 2007 4:49 PM Subject: Re: segmentation fault. (snip) in the past, i've gotten those segfaults from: reading a bad cookie

Re: catching a segmentation fault

On Thursday 17 May 2007 00:13, Tyler Bird wrote: I am setting up a new server with mod_perl + apache 2.0 + some legacy code and am sporadically rececing a segmentation fault to my apache logs like so. Maybe this helps: http://perl.apache.org/docs/2.0/devel/debug/c.html Is your code by chance

Re: catching a segmentation fault

Torsten Foertsch wrote: On Thursday 17 May 2007 00:13, Tyler Bird wrote: I am setting up a new server with mod_perl + apache 2.0 + some legacy code and am sporadically rececing a segmentation fault to my apache logs like so. Maybe this helps: http://perl.apache.org/docs/2.0/devel

Re: catching a segmentation fault

Are you running Apache 2.0 on Windows? Tyler Bird wrote: Hi all, I was wondering how I could use the %SIG has to catch a segmentation fault. I am setting up a new server with mod_perl + apache 2.0 + some legacy code and am sporadically rececing a segmentation fault to my apache logs like

AW: Segmentation fault(11) on AIX - searching the archive couldn' t solve my problem

) mod_perl/2.0.3 Perl/v5.8.2 configured -- resuming normal operations [Mon Jan 29 14:57:32 2007] [notice] child pid 860200 exit signal Segmentation fault (11) [Mon Jan 29 14:57:32 2007] [notice] child pid 745506 exit signal Segmentation fault (11) [Mon Jan 29 14:57:34 2007] [notice] child pid 745508 exit

Segmentation fault(11) on AIX - searching the archive couldn't so lve my problem

in the error_log: [Thu Jan 18 13:06:19 2007] [notice] IBM_HTTP_Server/2.0.47.1 Apache/2.0.47 (Unix) mod_perl/2.0.3 Perl/v5.8.2 configured -- resuming normal operations [Thu Jan 18 13:06:29 2007] [notice] child pid 790546 exit signal Segmentation fault (11) [Thu Jan 18 13:06:31 2007] [notice] child pid

Re: Segmentation fault(11) on AIX - searching the archive couldn't so lve my problem

[EMAIL PROTECTED] wrote: I've searched a lot throug the archive of this mailinglist and found lot's of postings also pointing to Segmentation fault (11), but usually the suggested solution was to have a look in the SUPPORT-file in the mod_perl directory. Actually, the suggested solution

Re: child pid 28464 exit signal Segmentation fault (11)

::Registry package modperl_mgv_resolve: [28464/3078568880] found `handler' in class `ModPerl::Registry' as a method [Sun Oct 08 17:19:55 2006] [notice] child pid 28464 exit signal Segmentation fault (11) modperl_perl_ids_get: pid=28487, ppid=28460, uid=33, euid=33, gid=33, egid=-1

Re: child pid 28464 exit signal Segmentation fault (11)

::Registry package modperl_mgv_resolve: [28464/3078568880] found `handler' in class `ModPerl::Registry' as a method [Sun Oct 08 17:19:55 2006] [notice] child pid 28464 exit signal Segmentation fault (11) modperl_perl_ids_get: pid=28487, ppid=28460, uid=33, euid=33, gid=33, egid=-1

Re: off topic - Re: child pid 28464 exit signal Segmentation fault (11)

- From: Cyril SCETBON [EMAIL PROTECTED] To: modperl@perl.apache.org Sent: Sunday, October 08, 2006 12:50 PM Subject: child pid 28464 exit signal Segmentation fault (11) Hi people, I get this error message int error.log when I try to access a perl script which exists or not. I've turned on trace

exit signal Segmentation fault (11) when asking for non-existent file/directories

I'm experiencing a strange but repeatable problem with mod_perl. Whenever I ask for a non-existent file that should be served by mod_perl, I have the following error: [Thu Oct 05 12:34:19 2006] [notice] child pid 22297 exit signal Segmentation fault (11) Here the file I'm asking: /cgi

exit signal Segmentation fault (11) when asking for non-existent file/directories

I'm experiencing a strange but repeatable problem with mod_perl. Whenever I ask for a non-existent file that should be served by mod_perl, I have the following error: [Thu Oct 05 12:34:19 2006] [notice] child pid 22297 exit signal Segmentation fault (11) Here the file I'm asking: /cgi

[Resurect] Re: SubRequest in Handler vs SubRequest in Filter - and Segmentation Fault

Which of these was the final verdict? I talked to Stas a while ago and he was for committing it which I'd like to do to resolve this issue. Stas Bekman wrote: Index: xs/Apache2/SubRequest/Apache2__SubRequest.h === ---

mod perl Apache2::SOAP Segmentation fault

Hello,I'm tring to config a Apache2::SOAP Module over a debian box:apache2apache2-commonapache2-mpm-prefork or apache2-mpm-worker or apache2-mpm-perchild (all tested)libapache2-mod-perl2 -- Kindly RegardsDavood FiroozianProud DeveloperOzino Group http://www.ozino.com

Re: mod perl Apache2::SOAP Segmentation fault

On Tuesday 01 August 2006 16:43, Davood Firoozian wrote: libapache2-mod-perl2 Debian stable unfortunately has a pre-release version of libapache2-mod-perl2. It is really, really not want you want to work with, so you may have to use backports. You'll find one at http://www.backports.org/

Re: SubRequest in Handler vs SubRequest in Filter - and Segmentation Fault

Scott Penrose wrote: [...] (gdb) bt #0 0xb7bef73d in modperl_wbucket_flush (wb=0x0, add_flush_bucket=0) at modperl_filter.c:236 #1 0xb7a7efaf in mpxs_ap_run_sub_req (r=0x84e1708) at Apache2__SubRequest.h:25 #2 0xb7a7f55b in XS_Apache2__SubRequest_run (cv=0x8351e78) at SubRequest.xs:83

Re: SubRequest in Handler vs SubRequest in Filter - and Segmentation Fault

After banging my head all day I have narrowed this down just a little... I had a terrible time working out WHY the Test code works but nothing else does. And I have finally solved that, but not why. The answer is which Handler for the original content being filtered. I added a simple

Re: SubRequest in Handler vs SubRequest in Filter - and Segmentation Fault

Scott Penrose wrote: Location /zx SetHandler modperl PerlResponseHandler Zaltana::ExpandTest::response PerlOutputFilterHAndler Zaltana::ExpandTest /Location Location /zx SetHandler default PerlOutputFilterHAndler Zaltana::ExpandTest /Location It should be noted that

Re: SubRequest in Handler vs SubRequest in Filter - and Segmentation Fault

You have two choices, 'modperl' OR 'perl-script'. 'default' is part of httpd core not a mod_perl extension. Thanks but that is correct and my intention. You have many choices, modperl and perl-script is only for perl, default-handler is for the built in default handler (basically files).

Re: SubRequest in Handler vs SubRequest in Filter - and Segmentation Fault

Scott Penrose wrote: On 05/07/2006, at 5:47, Stas Bekman wrote: http://perl.apache.org/docs/2.0/user/handlers/ filters.html#HTTP_Request_vs__Connection_Filters OK Some very weird and interesting problems here. I think they are bugs, but I am not certain. Firstly - if you write the

Re: SubRequest in Handler vs SubRequest in Filter - and Segmentation Fault

You can't test mod_perl modules from the command line, Scott. Only running under a mod_perl interpreter. Dooh. I didn't know that. Mine have always worked - I guess I just have not come across the thing that does not work :-) Until now. Right, that worked in mod_perl - still seg faults, so

Re: SubRequest in Handler vs SubRequest in Filter - and Segmentation Fault

Scott Penrose wrote: Is this a request or a connection filter? It won't work as a connection filter (r is not available there). It is an ouptut filter. But what output filter? There are two: http://perl.apache.org/docs/2.0/user/handlers/filters.html#HTTP_Request_vs__Connection_Filters

Re: SubRequest in Handler vs SubRequest in Filter - and Segmentation Fault

On 04/07/2006, at 17:30, Stas Bekman wrote: Scott Penrose wrote: Is this a request or a connection filter? It won't work as a connection filter (r is not available there). It is an ouptut filter. But what output filter? There are two: http://perl.apache.org/docs/2.0/user/handlers/

Re: SubRequest in Handler vs SubRequest in Filter - and Segmentation Fault

Scott Penrose wrote: On 04/07/2006, at 20:53, Scott Penrose wrote: On 04/07/2006, at 17:30, Stas Bekman wrote: Scott Penrose wrote: Is this a request or a connection filter? It won't work as a connection filter (r is not available there). It is an ouptut filter. But what output

Re: SubRequest in Handler vs SubRequest in Filter - and Segmentation Fault

On 05/07/2006, at 5:47, Stas Bekman wrote: http://perl.apache.org/docs/2.0/user/handlers/ filters.html#HTTP_Request_vs__Connection_Filters OK Some very weird and interesting problems here. I think they are bugs, but I am not certain. Firstly - if you write the code... (straight from the

Re: SubRequest in Handler vs SubRequest in Filter - and Segmentation Fault

Is this a request or a connection filter? It won't work as a connection filter (r is not available there). It is an ouptut filter. What's the core's backtrace? I will generate this tomorrow (don't have access to the machine today). Thanks Scott P.S. I have done a temporary work around

  1   2   >