Mailing-List: contact apreq-dev-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Received-SPF: pass (hermes.apache.org: domain of gcaa-apreq-dev@m.gmane.org
 designates 80.91.224.249 as permitted sender)
Mail-Followup-To: apreq-dev@httpd.apache.org
To: apreq-dev@httpd.apache.org
From: Joe Schaefer <joe+gmane@sunstarsys.com>
Subject: Re: test failed for libapreq2-2.04_03 on macos x
Date: 04 Sep 2004 11:01:18 -0400
Lines: 41
Message-ID: <87acw6qds1.fsf@gemini.sunstarsys.com>
References: <A58F34A8-FE80-11D8-92EE-000D9331B488@2bz.de>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Mail-Copies-To: never
User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.2
Sender: news <news@sea.gmane.org>

Boris Zentner <bzm@2bz.de> writes:

> Hi,
> I just installed perl 5.8.4 + apache2 2.0.50  + mod_perl 1.99_16 and
> libapreq2-2.04_03 on os x.
> 
> All tests for mod_perl worked fine.
> But for libapreq2 all cgi.t tests fail.

Exactly which cgi.t tests?  There are two sets (one in env/t, the other
in glue/perl/t/apreq).  Do the other tests all pass?

> It tried to build apache with and without ssl and libapreq2 as DSO and as
> static module inside apache. 

I don't think the tests work very well for static builds of libapreq, so
stick to DSO for running the tests.

> Every-time with the same result, all cgi.t tests fail.

[...]

> a backtrace in gdb shows this:
> 
> Program received signal EXC_BAD_ACCESS, Could not access memory.
> 0x002ebf90 in apreq_xs_request_get ()
> 
> #0  0x002ebf90 in apreq_xs_request_get ()
> #1  0x0136c6d0 in Perl_pp_entersub ()
> #2  0x0136503c in Perl_runops_standard ()
> #3  0x01311dc4 in Perl_call_sv ()
> #4  0x004535a8 in modperl_callback ()

The cgi.t tests use libapreq2 in a separate process from the server.
But this backtrace is from a server segfault.  We need more info
regarding the particular test (in glue/perl/t/apreq) that this 
backtrace represents.


-- 
Joe Schaefer