Upgrading libapreq2.17 to 2.18 / Debian bug report 1060765

2024-01-13 Thread Randolf Richardson
I submitted a bug report to Debian (Linux) about the libapreq2.17, indicating that upgrading to libapreq2.18 resolves the problem: Debian Bug report logs - #1060765 libapreq2-3: Apache2::Upload v2.17 clobbering remaining CGI parameters

mod_perl 2.0.1[01] bug report: svav_getstr

2020-06-18 Thread Peter Scott
h the possibility of a line being longer than bufsiz, and it is in practice called with bufsiz being a tiny number.  It needs to be able to save the rest of a long line to return on the next call. -8<-- Start Bug Report 8<-- 1. Problem Description:   [D

Re: [Bug Report] mod_perl runs with GID 0 !

2016-04-12 Thread John Dunlap
The only stupid question is the one you don't ask. On Tue, Apr 12, 2016 at 10:59 AM, Ruben Safir wrote: > On 04/12/2016 10:54 AM, Ben RUBSON wrote: > > The files created inside a directory will be owned by the group of the > directory, not by the primary group of the user which creates the file.

Re: [Bug Report] mod_perl runs with GID 0 !

2016-04-12 Thread Ruben Safir
On 04/12/2016 10:54 AM, Ben RUBSON wrote: > The files created inside a directory will be owned by the group of the > directory, not by the primary group of the user which creates the file... > This confused me... > > I'm really sorry for the useless noise :| its not noise. I learned something,

Re: [Bug Report] mod_perl runs with GID 0 !

2016-04-12 Thread Ben RUBSON
>> And what is a little bit frightening here is that Apache is launched by the >> #1025 user itself. >> So how could it be possible for it to generate a file owned by group #0... >> Very strange ! > > Something is misconfigured, but its not related to modperl. You're totally right, and I would l

Re: [Bug Report] mod_perl runs with GID 0 !

2016-04-12 Thread John D Groenveld
In message , Ben RUBSON writes: >And what is a little bit frightening here is that Apache is launched by the >#1025 user itself. >So how could it be possible for it to generate a file owned by group #0... >Very strange ! Something is misconfigured, but its not related to modperl. Disable modperl

Re: [Bug Report] mod_perl runs with GID 0 !

2016-04-12 Thread Ben RUBSON
>> Let's run the following example script in mod_perl : >> >> # more test.pl >> open(my $fh, ">", "/tmp/test.log"); >> print $fh "Your UID is " . $< . "\n"; >> my @groups = split '\s', $(; >> print $fh "You belong to these groups: "; >> print $fh $_ . " " foreach(@groups); > > How did you run the

Re: [Bug Report] mod_perl runs with GID 0 !

2016-04-12 Thread Ben RUBSON
>> Let's run the following example script in mod_perl : >> >> # more test.pl >> open(my $fh, ">", "/tmp/test.log"); >> print $fh "Your UID is " . $< . "\n"; >> my @groups = split '\s', $(; >> print $fh "You belong to these groups: "; >> print $fh $_ . " " foreach(@groups); > > How did you run the

Re: [Bug Report] mod_perl runs with GID 0 !

2016-04-12 Thread Ben RUBSON
>> Let's run the following example script in mod_perl : >> >> # more test.pl >> open(my $fh, ">", "/tmp/test.log"); >> print $fh "Your UID is " . $< . "\n"; >> my @groups = split '\s', $(; >> print $fh "You belong to these groups: "; >> print $fh $_ . " " foreach(@groups); > > How did you run the

Re: [Bug Report] mod_perl runs with GID 0 !

2016-04-12 Thread John D Groenveld
In message <88583f53-89d2-40aa-b850-cc819c5e6...@gmail.com>, Ben RUBSON writes: >Let's run the following example script in mod_perl : > ># more test.pl >open(my $fh, ">", "/tmp/test.log"); >print $fh "Your UID is " . $< . "\n"; >my @groups = split '\s', $(; >print $fh "You belong to these groups: "

Re: [Bug Report] mod_perl runs with GID 0 !

2016-04-12 Thread Ben RUBSON
>> Because this is the documented procedure : >> http://perl.apache.org/docs/2.0/user/help/help.html#Reporting_Problems >> > > Interesting. I don't ever recall seeing a bug report on this list. I > always assumed there to be a developed list. I had a look at t

Re: [Bug Report] mod_perl runs with GID 0 !

2016-04-12 Thread Ruben Safir
On 04/12/2016 02:11 AM, Ben RUBSON wrote: > Because this is the documented procedure : > http://perl.apache.org/docs/2.0/user/help/help.html#Reporting_Problems > Interesting. I don't ever recall seeing a bug report on this list. I always assumed there to be a developed li

Re: [Bug Report] mod_perl runs with GID 0 !

2016-04-11 Thread Ben RUBSON
Because this is the documented procedure : http://perl.apache.org/docs/2.0/user/help/help.html#Reporting_Problems > I'm confused. Why send this to the mailing list? > > > On Mon, Apr 11, 2016 at 11:04:17PM +0200, Ben RUBSON wrote: >> -----8<-- Star

Re: [Bug Report] mod_perl runs with GID 0 !

2016-04-11 Thread Ruben Safir
I'm confused. Why send this to the mailing list? On Mon, Apr 11, 2016 at 11:04:17PM +0200, Ben RUBSON wrote: > -8<------ Start Bug Report 8<-- > 1. Problem Description: > > Hello, > > Here is my Apache user and group

[Bug Report] mod_perl runs with GID 0 !

2016-04-11 Thread Ben RUBSON
-8<-- Start Bug Report 8<-- 1. Problem Description: Hello, Here is my Apache user and group : # grep -iE "user|group" httpd.conf User #1025 Group #1025 # ps axo uid,gid,comm | grep http 1025 1025 httpd 1025 1025 httpd 1025 1025

mod_perl-2.0.8 bug report - make test fails - FreeBSD

2014-01-17 Thread Rick Sattler
-8<-- Start Bug Report 8<-- 1. Problem Description:  I am having trouble running "make test" using the latest mod_perl version 2.0.8 on my FreeBSD system. I receive the following error message: /usr/local/bin/perl5.18.1 -Iblib/arch -Iblib/li

mod_perl-2.0.8 bug report - make test fails - FreeBSD

2014-01-17 Thread Rick Sattler
line 977. ++ | Please file a bug report: http://perl.apache.org/bugs/ | ++ *** Error code 13 Stop. make[1]: stopped in /usr/ports/www/mod_perl2/work/mod_perl-2.0.8 *** Error code 1 (ignored)   As requested,

bug report: Perl variable expansion in build directory path (very minor)

2013-09-13 Thread Thomas M. Payerle
-8<-- Start Bug Report 8<-- 1. Problem Description: Perl variable expansion in build directory path (very minor) In t/conf/extra.last.conf.in, lines 115-138, there are three places where $PerlConfig or @PerlConfig is being set to values cont

Re: Bug report: #0 file_dup (new_file=0xbfd296d4, old_file=0x0, p=0x80a70a8, which_dup=1) at file_io/unix/filedup.c:59 segfault

2011-05-05 Thread A. Przygienda
After experimenting around, the reason is the global directive I use (perfectly valid) ErrorLog syslog:local6 that crashes #ifdef MP_TRACE /* httpd core open_logs handler re-opens s->error_log, which might * change, even though it still points to the same physical file * (.e.g on w

Re: Bug report: #0 file_dup (new_file=0xbfd296d4, old_file=0x0, p=0x80a70a8, which_dup=1) at file_io/unix/filedup.c:59 segfault

2011-05-05 Thread A. Przygienda
Same problem on 2.0.5 and gentoo 2010 That's how I run it r -D SSL -D SSL_DEFAULT_VHOST -D DEFAULT_VHOST -D INFO -D DAV -D DAV_FS -D CACHE -D MEM_CACHE -D PHP5 -D PERL_VHOST -D PYTHON -D STATUS -D PROXY -D PROXY_HTML -d /usr/lib/apache2 -f /etc/apache2/httpd.conf -E /var/log/apache2/startuperror.

possible make test bug report

2011-04-05 Thread Rich Reamer
Hello, Output from "REPORT" -8<------ Start Bug Report 8<-- 1. Problem Description: I am getting this error from (make test) of the mod_perl module. snippet from error_log: [Tue Apr 05 12:16:41 2011] [notice] Apache/2.2.16 (Debian) world d

Re: Bug report: #0 file_dup (new_file=0xbfd296d4, old_file=0x0, p=0x80a70a8, which_dup=1) at file_io/unix/filedup.c:59 segfault

2011-03-19 Thread A. Przygienda
-8<------ Start Bug Report 8<-- >> 1. Problem Description: >> >> Crash gentoo apache2 start. core dump below, think tries to dup >> a 0 file pointer >> >> >> [DESCRIBE THE PROBLEM HERE] >> >> 2. U

Re: Bug report: #0 file_dup (new_file=0xbfd296d4, old_file=0x0, p=0x80a70a8, which_dup=1) at file_io/unix/filedup.c:59 segfault

2011-03-19 Thread Fred Moyer
Have you tried 2.0.5? On Sat, Mar 19, 2011 at 9:15 AM, A. Przygienda wrote: > -8<-- Start Bug Report 8<-- > 1. Problem Description: > >  Crash gentoo apache2 start. core dump below, think tries to dup >  a 0 file pointer > > &g

Bug report: #0 file_dup (new_file=0xbfd296d4, old_file=0x0, p=0x80a70a8, which_dup=1) at file_io/unix/filedup.c:59 segfault

2011-03-19 Thread A. Przygienda
-8<-- Start Bug Report 8<-- 1. Problem Description: Crash gentoo apache2 start. core dump below, think tries to dup a 0 file pointer [DESCRIBE THE PROBLEM HERE] 2. Used Components and their Configuration: *** mod_perl version 2.04 ***

[mp2] sendfile() bug report with Apache-Test test attached

2009-06-25 Thread Adriano Caloiaro
0 2533148 "-" "-" *.*.*.* - - [18/Jun/2009:10:11:45 -0400] "GET /mygcx/test/flvplayernew17.flv HTTP/1.1" 200 2533148 "-" "-" *.*.*.* - - [18/Jun/2009:10:11:45 -0400] "GET /mygcx/test/flvplayernew17.flv HTTP/1.1" 200 2533148 "-" "-&qu

Re: bug report: wrong line number if using built-in functions

2008-06-19 Thread Philippe M. Chiasson
Christian Mehring wrote: -8<-- Start Bug Report 8<-- 1. Problem Description: Line numbers will be wrong if a bulit-in function's first parameter is not in the same line. Minimized example: 01: #!/usr/local/bin/perl 02: use strict; 03: use w

bug report: wrong line number if using built-in functions

2008-06-19 Thread Christian Mehring
-8<-- Start Bug Report 8<-- 1. Problem Description: Line numbers will be wrong if a bulit-in function's first parameter is not in the same line. Minimized example: 01: #!/usr/local/bin/perl 02: use strict; 03: use warnings; 04: 05: abs 06: 0

[mp2] bug report

2008-06-15 Thread Frank San Filippo
[Sun Jun 15 14:13:59 2008] [error] [client 127.0.0.1] user stas: authentication failure for "/": Password Mismatch [Sun Jun 15 14:14:01 2008] [info] Child process pid=13461 is exiting [Sun Jun 15 14:14:01 2008] [info] Child process pid=13461 is exiting - server pu sh END in modperl_extra.pl, pid=13

Re: resend: [mp2] bug report - heap management error in mod_perl on Windows

2008-01-04 Thread Randy Kobes
On Sun, 30 Dec 2007, Randy Kobes wrote: On Sat, 29 Dec 2007, Tom Donovan wrote: mod_perl re-defines "perl_free" as "free" in modperl_perl_includes.h:69. This causes an attempt to use the native Windows free() function to release memory which should be released by the perl_free() function loc

Re: resend: [mp2] bug report - heap management error in mod_perl on Windows

2007-12-30 Thread William A. Rowe, Jr.
Randy Kobes wrote: Hi Tom, Thanks for the detailed report, and patch. I tried out the patch with perl-5.8.8, compiled against Apache/2.2.4, and all the tests passed. However, the restart problem still remains; evidently, http://issues.apache.org/bugzilla/show_bug.cgi?id=43534 or something

Re: resend: [mp2] bug report - heap management error in mod_perl on Windows

2007-12-29 Thread Randy Kobes
On Sat, 29 Dec 2007, Tom Donovan wrote: mod_perl re-defines "perl_free" as "free" in modperl_perl_includes.h:69. This causes an attempt to use the native Windows free() function to release memory which should be released by the perl_free() function located in PerlXXX.dll. The specific call i

resend: [mp2] bug report - heap management error in mod_perl on Windows

2007-12-29 Thread Tom Donovan
ree free # undef free # endif #endif -8<-- Start Bug Report 8<-- 1. Problem Description: Heap errors on Windows with mod_perl (trunk), Perl 5.10.0, and Apache 2.2 (SVN 2.2.x branch) Also observed with mod_perl 2.0.3, ActiveState Perl 5.8.8

Re: Bug report - mod_perl2 make test fails on Cygwin DLL version: 1.5.24

2007-11-05 Thread Nikolay Ananiev
Find the output from REPORT below. Basically everything seems to build ok but make test fails with the claim that the server didn't start. When I look at the ps output I can see that httpd2 has started. Any help appreciated. Thanks, Rolf -----8<------ Start

Bug report - mod_perl2 make test fails on Cygwin DLL version: 1.5.24

2007-10-27 Thread Rolf Banting
hanks, Rolf -8<-- Start Bug Report 8<-- 1. Problem Description: make test fails: /usr/bin/perl.exe -Iblib/arch -Iblib/lib \ t/TEST -clean APACHE_TEST_GROUP= APACHE_TEST_HTTPD= APACHE_TEST_PORT= APACHE_TEST_USER= APACHE_TEST_APXS= \

Re: resend: Bug report re: Apache 2.2.6 on Windows

2007-09-18 Thread Tom Donovan
Michael Lackhoff wrote: On 18.09.2007 15:47 William A. Rowe, Jr. wrote: Hmm, I don't understand this, so I cannot say how serious it could be. My question is: Should I stick with 2.0.59 or upgrade with a patched 2.0.61/2.2.6? This is a production server and the change log lists quite a few sec

Re: resend: Bug report re: Apache 2.2.6 on Windows

2007-09-18 Thread William A. Rowe, Jr.
Michael Lackhoff wrote: > On 18.09.2007 15:47 William A. Rowe, Jr. wrote: > > Hmm, I don't understand this, so I cannot say how serious it could be. > My question is: Should I stick with 2.0.59 or upgrade with a patched > 2.0.61/2.2.6? > This is a production server and the change log lists quite a

Re: resend: Bug report re: Apache 2.2.6 on Windows

2007-09-18 Thread Michael Lackhoff
On 18.09.2007 15:47 William A. Rowe, Jr. wrote: > Yes, of course. However in the second case, you do not have an inheritable > file handle. apr_file_dup simply dups the handle in the current process, > so the patch can't possibly have the desired effect. > > There is a real concern; under what

Re: resend: Bug report re: Apache 2.2.6 on Windows

2007-09-18 Thread William A. Rowe, Jr.
Tom Donovan wrote: > Michael Lackhoff wrote: >> On 23.12.37378 20:59 Tom Donovan wrote: >> >>> 1. Problem Description: >>> >>> perl-script handler fails with Apache 2.2.6 on Windows >>> due to changes in stdin/stdout/stderr handles in mpm_winnt >>> >>> Problem occurs with mod_perl 2.0.3 or wi

Re: resend: Bug report re: Apache 2.2.6 on Windows

2007-09-18 Thread Tom Donovan
Michael Lackhoff wrote: On 23.12.37378 20:59 Tom Donovan wrote: 1. Problem Description: perl-script handler fails with Apache 2.2.6 on Windows due to changes in stdin/stdout/stderr handles in mpm_winnt Problem occurs with mod_perl 2.0.3 or with current (9/14/2007) SVN trunk. I no

Re: resend: Bug report re: Apache 2.2.6 on Windows

2007-09-18 Thread Michael Lackhoff
On 23.12.37378 20:59 Tom Donovan wrote: > 1. Problem Description: > > perl-script handler fails with Apache 2.2.6 on Windows > due to changes in stdin/stdout/stderr handles in mpm_winnt > > Problem occurs with mod_perl 2.0.3 or with > current (9/14/2007) SVN trunk. I noticed the same

Re: resend: Bug report re: Apache 2.2.6 on Windows

2007-09-14 Thread William A. Rowe, Jr.
William A. Rowe, Jr. wrote: > > is that mod perl is attempting to protect us from ourselves even before > the fixes went into win32. Of all of the adjustments in version 2.2.6, > try backing out only this single effect of the patch, which closed stdin > on both the parent and child, and please co

Re: resend: Bug report re: Apache 2.2.6 on Windows

2007-09-14 Thread William A. Rowe, Jr.
Tom Donovan wrote: > > -8<-- Start Bug Report 8<-- > 1. Problem Description: > > perl-script handler fails with Apache 2.2.6 on Windows > due to changes in stdin/stdout/stderr handles in mpm_winnt > > Problem occu

resend: Bug report re: Apache 2.2.6 on Windows

2007-09-14 Thread Tom Donovan
Original Message Subject: Bug report Date: Fri, 14 Sep 2007 10:27:19 -0400 From: Tom Donovan <[EMAIL PROTECTED]> Reply-To: [EMAIL PROTECTED] To: modperl@perl.apache.org -8<-- Start Bug Report 8<-- 1. Problem Description:

Re: bug report

2007-05-23 Thread Fred Moyer
LWP: 5.65 mod_perl : 1.9907 It looks like you have a very old version of mod_perl2 installed in addition to the one you just installed. I can't say whether that's the cause of the server not starting during 'make test', but it might help to remove it via rpm or what

bug report

2007-05-23 Thread Neil Gast
-8<-- Start Bug Report 8<-- 1. Problem Description: Got the following output from 'make test': still waiting for s

Re: Bug Report

2007-01-04 Thread Robert Landrum
Snook, Adrian (London) wrote: 3. This is the core dump trace: (if you get a core dump): Core was generated by `/home -k start'. Program terminated with signal 11, Segmentation fault. #0 0x002f201e in free () from /lib/tls/libc.so.6 (gdb) bt full #0 0x002f201e in free () from /lib/tls/libc.so

Re: bug report : "make test" failure when compiling from source.

2006-09-19 Thread Philip M. Gollucci
Daniel McBrearty wrote: 1. Problem Description: Trying to build and install mod_perl from source. Have already built perl and apache 2.2 from source, they both seem to be fine (latest stable, both). But it is my first cut at this, so I could have made a dumb error. Anyhow, all help appreciated.

bug report : "make test" failure when compiling from source.

2006-09-19 Thread Daniel McBrearty
1. Problem Description: Trying to build and install mod_perl from source. Have already built perl and apache 2.2 from source, they both seem to be fine (latest stable, both). But it is my first cut at this, so I could have made a dumb error. Anyhow, all help appreciated. "make test" fails. Here

[mp2] bug report - incorrect @ARGV split in xs/APR/APR/Makefile.PL

2006-06-13 Thread Sergey Skvortsov
1. Problem Description: The next line in xs/APR/APR/Makefile.PL: %args = map { split /=/, $_ } @ARGV; is incorrect because splits all occurencies of '=' sumbol, while only first one must be catched. To reproduce error just build mod_perl2 with: CFLAGS= -O2 -pipe -march=pentium4 Solution: ---

[mp2] Bug report - "make test" t/perlrun_extload failures

2006-04-17 Thread LUK ShunTim
install/install.html#Static_mod_perl There are 2 "make test" failures running t/perlrun_extload. Same result with the current stable release as well as the svn version. I'm going to use mod_perl with Apache::ASP. Is this bug (assuming it is one) critical in deployment? ---

Re: Bug report $r->read() fail

2006-03-07 Thread Philippe M. Chiasson
Khai Doan wrote: > -8<-- Start Bug Report 8<-- > 1. Problem Description: > >Calling $r->read($buf,0) result in an internal server error, and an entry > in error_log: The LENGTH argument can't be negative at . A sli

Bug report $r->read() fail

2006-03-06 Thread Khai Doan
-8<-- Start Bug Report 8<-- 1. Problem Description: Calling $r->read($buf,0) result in an internal server error, and an entry in error_log: The LENGTH argument can't be negative at . 2. Used Components and their Configuration:

Re: Bug report: ModPerl 2.0.2 make test "Insecure directory under -T"

2005-12-23 Thread Stas Bekman
Stas Bekman wrote: Kent, Mr. John (Contractor) wrote: Hello Stas, No, my path does not contain . or .. anywhere. Here is what I get: [EMAIL PROTECTED] ~]$ perl -le 'print $ENV{PATH}' /users/webuser/perl/bin:/users/webuser/apache-ant/bin:users/webuser/netscape:/users/webuser/mysql/bin:/users/w

Re: Bug report: ModPerl 2.0.2 make test "Insecure directory under -T"

2005-12-23 Thread Stas Bekman
Kent, Mr. John (Contractor) wrote: Hello Stas, No, my path does not contain . or .. anywhere. Here is what I get: [EMAIL PROTECTED] ~]$ perl -le 'print $ENV{PATH}' /users/webuser/perl/bin:/users/webuser/apache-ant/bin:users/webuser/netscape:/users/webuser/mysql/bin:/users/webuser/jdev/bin:/user

RE: Bug report: ModPerl 2.0.2 make test "Insecure directory under -T"

2005-12-23 Thread Kent, Mr. John \(Contractor\)
3:04 PM To: Kent, Mr. John (Contractor) Cc: Mod-Perl (E-mail) Subject: Re: Bug report: ModPerl 2.0.2 make test "Insecure directory under -T" Kent, Mr. John (Contractor) wrote: > Here is mybugreport: > > ---------8<-- Start Bug Report 8<

Re: Bug report: ModPerl 2.0.2 make test "Insecure directory under -T"

2005-12-22 Thread Stas Bekman
Kent, Mr. John (Contractor) wrote: Here is mybugreport: -8<-- Start Bug Report 8<-- 1. Problem Description: [DESCRIBE THE PROBLEM HERE] When running >make test Get the following errror [Thu Dec 22 09:28:15 2005] [info] base server + 27 vhosts

Bug report: ModPerl 2.0.2 make test "Insecure directory under -T"

2005-12-22 Thread Kent, Mr. John \(Contractor\)
Here is mybugreport: -8<-- Start Bug Report 8<-- 1. Problem Description: [DESCRIBE THE PROBLEM HERE] When running >make test Get the following errror [Thu Dec 22 09:28:15 2005] [info] base server + 27 vhosts ready to run tests [Thu Dec 22 09:2

Re: Reference to: mod_perl2 bug report [message #924360]

2005-09-27 Thread Philip M. Gollucci
Hi, [EMAIL PROTECTED] wrote: http://www.issociate.de/board/post/244105/mod_perl2_bug_report.html >1. Problem Description: > >I'm trying to install mod_perl2, but i've got a problem. > >I've successfully compiled apache 2.054, mod_perl2, and the next step >is running 'make test' command into fo

Reference to: mod_perl2 bug report [message #924360]

2005-09-26 Thread [EMAIL PROTECTED]
I'have the exact same error/problem in my environment as mentioned here: http://www.issociate.de/board/post/244105/mod_perl2_bug_report.html However, I'm a little unclear of the details of the fix due to my inexperience with FreeBSD. I was hoping that someone could explain this fix in further d

Re: mod_perl2 bug report

2005-08-16 Thread Philip M. Gollucci
Stas Bekman wrote: Philip M. Gollucci wrote: Well, the diagnostics are not exactly correct, Philip. as the problem has little to do with perl having ithreads enabled. apr_os_thread_current is used only if APR_HAS_THREADS is defined. When mod_perl is being built it gets this define from the ap

Re: mod_perl2 bug report

2005-08-16 Thread Stas Bekman
Philip M. Gollucci wrote: During the tests i've an error: /home/asm/apache2054/bin/bin/httpd -d /usr/home/asm/soft/Apache/mod_perl-2.0.1/t -f /usr/home/asm/soft/Apache/mod_perl-2.0.1/t/conf/httpd.conf -D APACHE2 -D PERL_USEITHREADS using Apache/2.0.54 (prefork MPM) waiting 120 seconds for

Re: mod_perl2 bug report

2005-08-16 Thread Philip M. Gollucci
During the tests i've an error: /home/asm/apache2054/bin/bin/httpd -d /usr/home/asm/soft/Apache/mod_perl-2.0.1/t -f /usr/home/asm/soft/Apache/mod_perl-2.0.1/t/conf/httpd.conf -D APACHE2 -D PERL_USEITHREADS using Apache/2.0.54 (prefork MPM) waiting 120 seconds for server to start: .Syntax err

mod_perl2 bug report

2005-08-16 Thread Alexander Smotrov
local/lib/perl5/site_perl . *** Packages of interest status: Apache2: - Apache2::Request : - CGI: 3.06 ExtUtils::MakeMaker: 6.21 LWP: 5.76, 5.76 mod_perl : - mod_perl2 : 2.01 3. This is the core dump trace: (if you get a core dump): [CORE TRACE COMES HERE] This report was generated by t/REPORT on Tue Aug 16 10:23:59 2005 GMT. -8<-- End Bug Report --8<--

Re: [MP2] Bug Report - Segfault when using Image::Magick

2005-06-11 Thread Stas Bekman
William McKee wrote: On Tue, Jun 07, 2005 at 11:40:49PM +1000, Stas Bekman wrote: Something is not right here. Your perl is not threaded: However the segfault shows threads operation: #0 0x882fa1d7 in kill () from /lib/libc.so.5 (gdb) bt #0 0x882fa1d7 in kill () from /lib/libc.so.5 #1 0x

Re: [MP2] Bug report - errors when compiling with MP_DEBUG flag

2005-06-11 Thread Stas Bekman
William McKee wrote: [...] If you look at the linking command that you've pasted in the original report it had: /usr/local/src/httpd-2.0.54/srclib/apr/libapr-0.la which is the one that you need to check. Actually, I had taken a look in that file but there's nothing being defined in there.

Re: [MP2] Bug Report - Segfault when using Image::Magick

2005-06-11 Thread Stas Bekman
William McKee wrote: On Tue, Jun 07, 2005 at 11:40:49PM +1000, Stas Bekman wrote: Something is not right here. Your perl is not threaded: However the segfault shows threads operation: Yeah, it's bizarre. #0 0x882fa1d7 in kill () from /lib/libc.so.5 (gdb) bt #0 0x882fa1d7 in kill () fr

Re: [MP2] Bug Report - Segfault when using Image::Magick

2005-06-09 Thread William McKee
On Tue, Jun 07, 2005 at 11:40:49PM +1000, Stas Bekman wrote: > Something is not right here. Your perl is not threaded: > > However the segfault shows threads operation: Yeah, it's bizarre. > >#0 0x882fa1d7 in kill () from /lib/libc.so.5 > >(gdb) bt > >#0 0x882fa1d7 in kill () from /lib/libc.s

Re: [MP2] Bug report - errors when compiling with MP_DEBUG flag

2005-06-09 Thread William McKee
On Tue, Jun 07, 2005 at 11:35:46PM +1000, Stas Bekman wrote: > That's OK, William. But you aren't after defined symbols in .so, you are > after the APR_HAS_THREADS define which should be undef. Moreover, you are > building a static version so the symbols aren't coming from .so but .a/.la > archi

Re: [MP2] Bug Report - Segfault when using Image::Magick

2005-06-07 Thread Stas Bekman
William McKee wrote: -8<-- Start Bug Report 8<-- 1. Problem Description: When using Image::Magick (either 6.1.9.4 or 6.2.3) under mod_perl, the server segfaults. Used at the command line or under mod_cgi there are no errors. A core dump is attached

Re: [MP2] Bug report - errors when compiling with MP_DEBUG flag

2005-06-07 Thread Stas Bekman
William McKee wrote: On Tue, Jun 07, 2005 at 09:34:29AM +1000, Stas Bekman wrote: William, as you can see from the source src/modules/perl/modperl_util.h #if defined(MP_TRACE) && defined(APR_HAS_THREADS) #define MP_TRACEf_TID "/tid 0x%lx" #define MP_TRACEv_TID (unsigned long)apr_os_thread_

[MP2] Bug Report - Segfault when using Image::Magick

2005-06-06 Thread William McKee
-8<-- Start Bug Report 8<-- 1. Problem Description: When using Image::Magick (either 6.1.9.4 or 6.2.3) under mod_perl, the server segfaults. Used at the command line or under mod_cgi there are no errors. A core dump is attached. This is my first atte

Re: [MP2] Bug report - errors when compiling with MP_DEBUG flag

2005-06-06 Thread William McKee
n modperl_util.h, it appears to have worked. I'll submit my bug report in a separate email. Thanks, William -- Knowmad Services Inc. http://www.knowmad.com

Re: [MP2] Bug report - errors when compiling with MP_DEBUG flag

2005-06-06 Thread Stas Bekman
William McKee wrote: On Sat, Jun 04, 2005 at 09:29:53PM +1000, Stas Bekman wrote: /stubs/usr_local/src/mod_perl-2.0.0/src/modules/perl/modperl_util.c:472: undefined reference to `apr_os_thread_current' *** Error code 1 William, please try: http://perl.apache.org/docs/2.0/user/troubleshooting

Re: [MP2] Bug report - errors when compiling with MP_DEBUG flag

2005-06-05 Thread William McKee
On Sat, Jun 04, 2005 at 09:29:53PM +1000, Stas Bekman wrote: > >/stubs/usr_local/src/mod_perl-2.0.0/src/modules/perl/modperl_util.c:472: > >undefined reference to `apr_os_thread_current' > >*** Error code 1 > > William, please try: > http://perl.apache.org/docs/2.0/user/troubleshooting/troublesho

Re: [MP2] Bug report - errors when compiling with MP_DEBUG flag

2005-06-04 Thread Stas Bekman
William McKee wrote: -8<-- Start Bug Report 8<-- 1. Problem Description: While trying to track down a segfault that is occurring with Image::Magick, I went to build a version of mod_perl with debugging flags. Unfortunately this does not build for me

[MP2] Bug report - errors when compiling with MP_DEBUG flag

2005-06-02 Thread William McKee
-8<-- Start Bug Report 8<-- 1. Problem Description: While trying to track down a segfault that is occurring with Image::Magick, I went to build a version of mod_perl with debugging flags. Unfortunately this does not build for me under FreeBSD 5.3. H

Re: Bug Report : problem with both_str_native_remove test and broken mod_perl.so

2005-04-05 Thread Torsten Foertsch
On Monday 04 April 2005 19:39, Fred Seibel wrote: > t/filter/both_str_native_remove.# Failed test 1 in > t/filter/both_str_native_remove.t at line 22 > # Failed test 2 in t/filter/both_str_native_remove.t at line 24 > t/filter/both_str_native_remove.FAILED tests 1-2 > Faile

Re: Bug Report : problem with both_str_native_remove test and broken mod_perl.so

2005-04-04 Thread Stas Bekman
Fred Seibel wrote: 1. Problem Description: I cannot get a clean make test. the tests fail (but not consistently t/filter/both_str_native_remove.# Failed test 1 in t/filter/both_str_native_remove.t at line 22 # Failed test 2 in t/filter/both_str_native_remove.t at line 24 t/filter/both_st

Bug Report : problem with both_str_native_remove test and broken mod_perl.so

2005-04-04 Thread Fred Seibel
laddons/lib/perl5/vendor_perl . *** Packages of interest status: Apache::Request: - CGI: 3.05 LWP : 5.803 mod_perl : 1.999021 3. This is the core dump trace: (if you get a core dump): [CORE TRACE COMES HERE] This report was generated by t/REPORT on Mon Apr 4 17:23:33 2005 GMT. -8<-- End Bug Report --8<-- Note: Complete the rest of the details and post this bug report to modperl perl.apache.org. To subscribe to the list send an empty email to [EMAIL PROTECTED]

Re: Bug Report: seg fault with 1.29/Apache 1.3.33/RedHat 7.1

2004-11-20 Thread Tim Evans
On Fri, 19 Nov 2004 08:42:54 -0600 (CST), Brian Stevens wrote > Have you tried building mod_perl statically into httpd (rather than > as a DSO)? Thanks for your reply. While we'd covered this previously in the chain of e-mails, I should have added it here, too, for completeness. Static or dyn

Re: Bug Report: seg fault with 1.29/Apache 1.3.33/RedHat 7.1

2004-11-19 Thread Stas Bekman
[CC'ing Michael Schroeder who submitted a related patch to p5p http://www.gossamer-threads.com/lists/perl/porters/187753] Tim Evans wrote: so at the moment the solution is to recompile perl with -DPERL_USE_SAFE_PUTENV Does not work. Michael, do you have any other solutions for Tim? He seems to ha

Re: Bug Report: seg fault with 1.29/Apache 1.3.33/RedHat 7.1

2004-11-19 Thread Joe Schaefer
Tim Evans <[EMAIL PROTECTED]> writes: > Let it build apache for me; apache's config.status says: [...] > "--with-layout=Apache" \ [...] > Attaching to program: /usr/sbin/httpd, process 22798 Wrong httpd binary- the symbols in that stack trace are from a 2.0 server. Your server's path should

Re: Bug Report: seg fault with 1.29/Apache 1.3.33/RedHat 7.1

2004-11-19 Thread ___cliff rayman___
Tim Evans wrote: LoadModule php4_modulelibexec/libphp4.so LoadModule perl_modulelibexec/libperl.so Restart apache. Seg faults on simple test.php page. Error log says (same as before): [Thu Nov 18 20:48:17 2004] [notice] child pid 22818 exit signal Segmentation fault (11) I alw

Re: Bug Report: seg fault with 1.29/Apache 1.3.33/RedHat 7.1

2004-11-19 Thread Tim Evans
>so at the moment the solution is to recompile perl with >-DPERL_USE_SAFE_PUTENV Does not work. [EMAIL PROTECTED] apache_1.3.33]# perl -V:cppflags cppflags='-DPERL_USE_SAFE_PUTENV -fno-strict-aliasing -pipe -I/usr/local/include -I/usr/include/gdbm'; Fresh build of PHP 4.3.9; config.status h

Re: Bug Report: seg fault with 1.29/Apache 1.3.33/RedHat 7.1

2004-11-16 Thread Tim Evans
On Tue, 16 Nov 2004 16:00:19 -0500, Stas Bekman wrote > so at the moment the solution is to recompile perl with > -DPERL_USE_SAFE_PUTENV I'll give this a try in the next day or so. > not sure about: > >* Replace all PHP calls to putenv() with apache_setenv(). I read this as an either red

Re: Bug Report: seg fault with 1.29/Apache 1.3.33/RedHat 7.1

2004-11-16 Thread Stas Bekman
Tim Evans wrote: On Tue, 16 Nov 2004 16:00:19 -0500, Stas Bekman wrote so at the moment the solution is to recompile perl with -DPERL_USE_SAFE_PUTENV I'll give this a try in the next day or so. not sure about: * Replace all PHP calls to putenv() with apache_setenv(). I read this as an eith

Re: Bug Report: seg fault with 1.29/Apache 1.3.33/RedHat 7.1

2004-11-16 Thread Stas Bekman
Tim Evans wrote: Here's something more of interest (more than a year old, but the described symptons are spot-on: http://www.phpbuilder.com/lists/php-install/2003092/0018.php An excellent find, Tim. Funny but this exact problem is now discussed on p5p: http://www.gossamer-threads.com/lists/perl/

Re: Bug Report: seg fault with 1.29/Apache 1.3.33/RedHat 7.1

2004-11-16 Thread Tim Evans
Here's something more of interest (more than a year old, but the described symptons are spot-on: http://www.phpbuilder.com/lists/php-install/2003092/0018.php -- Tim Evans, TKEvans.com, Inc.|5 Chestnut Court [EMAIL PROTECTED] |Owings Mills, MD 21117 http://www.tkevans.c

Re: Bug Report: seg fault with 1.2

2004-11-15 Thread Stas Bekman
Stas Bekman wrote: Tim Evans wrote: So what are the differences? I suppose you want to compare 1) the options passed to ./configure 2) linker and compilation options (since mod_perl inserts the options suggested by Perl (see perl -V) when compiling the rest of the Apache modules and the Apache co

Re: Bug Report: seg fault with 1.2

2004-11-15 Thread Stas Bekman
Tim Evans wrote: So what are the differences? I suppose you want to compare 1) the options passed to ./configure 2) linker and compilation options (since mod_perl inserts the options suggested by Perl (see perl -V) when compiling the rest of the Apache modules and the Apache core. For PHP: ./con

Re: Bug Report: seg fault with 1.2

2004-11-15 Thread Tim Evans
>So what are the differences? I suppose you want to compare >1) the options passed to ./configure >2) linker and compilation options (since mod_perl inserts the options >suggested by Perl (see perl -V) when compiling the rest of the Apache >modules and the Apache core. For PHP: ./configure --w

Re: Bug Report: seg fault with 1.29/Apache 1.3.33/RedHat 7.1

2004-11-15 Thread Tim Evans
>Because you are running under gdb. If you run normally and arrange for the >system to allow the core files (as explained in the doc) you will get one.' > >Now how do you know that the process 3196 is the one that serves the >request? I assume that you run under httpd -X? But it doesn't seem to

Re: Bug Report: seg fault with 1.29/Apache 1.3.33/RedHat 7.1

2004-11-15 Thread Tim Evans
>The fact that you refuse to give us the segfault backtrace makes it really >hard to make any intelligent guesswork. There is no core file. gdb/bt on the running httpd process says: [EMAIL PROTECTED] src]# gdb httpd 3196 GNU gdb Red Hat Linux (5.2-2) Copyright 2002 Free Software Foundation, In

Re: Bug Report: seg fault with 1.29/Apache 1.3.33/RedHat 7.1

2004-11-14 Thread Stas Bekman
Tim Evans wrote: Because you are running under gdb. If you run normally and arrange for the system to allow the core files (as explained in the doc) you will get one.' Now how do you know that the process 3196 is the one that serves the request? I assume that you run under httpd -X? But it doesn

Re: Bug Report: seg fault with 1.29/Apache 1.3.33/RedHat 7.1

2004-11-14 Thread Stas Bekman
Tim Evans wrote: The fact that you refuse to give us the segfault backtrace makes it really hard to make any intelligent guesswork. There is no core file. gdb/bt on the running httpd process says: [EMAIL PROTECTED] src]# gdb httpd 3196 [...] Attaching to program: /usr/local/src/apache_1.3.33/src

Re: Bug Report: seg fault with 1.29/Apache 1.3.33/RedHat 7.1

2004-11-13 Thread Stas Bekman
Tim Evans wrote: 1.29 sees overly sensitive to small errors in html documents that a browser would ignor, returning empty documents to browser and logging seg faults to apache error log. [...] Makefile.PL options: perl Makefile.PL USE_DSO=1 httpd.conf: LoadModule perl_modulelibexec/libper

Bug Report: seg fault with 1.29/Apache 1.3.33/RedHat 7.1

2004-11-13 Thread Tim Evans
1.29 sees overly sensitive to small errors in html documents that a browser would ignor, returning empty documents to browser and logging seg faults to apache error log. Details >From Apache error log: [Fri Nov 12 12:28:23 2004] [notice] Apache/1.3.33 (Unix) mod_perl/1.29 PHP/4.3.9

Re: Bug report

2004-09-30 Thread Stas Bekman
[EMAIL PROTECTED] wrote: -8<-- Start Bug Report 8<-- 1. Problem Description: test server didn't start (t/logs/error_log): Leo, have you by chance read the suggestion that was printed out when 'make test' has aborted. Please try again a

Bug report

2004-09-29 Thread leo
-8<-- Start Bug Report 8<-- 1. Problem Description: test server didn't start (t/logs/error_log): [Tue Sep 28 15:55:11 2004] [info] mod_unique_id: using ip addr 10.0.153.5 [Tue Sep 28 15:55:12 2004] [info] Init: Initializing OpenSSL library [Tu

Re: bug report question

2004-06-24 Thread Geoffrey Young
John Wittkoski wrote: > The sample bug report (using t/REPORT) says to send bug reports to dev > perl.apache.org, but the web page under "Reporting Information" (at > http://perl.apache.org/docs/2.0/user/help/help.html#Reporting_Problems) > seems to indicate bugs shoul

  1   2   >