----- Original Message -----
From: "Randy Kobes" <[EMAIL PROTECTED]>
To: "pascal barbedor" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Monday, May 06, 2002 4:03 PM
Subject: Re: Pb with Win32 Installation


> On Mon, 6 May 2002, pascal barbedor wrote:
> >
> > I have the same problem : contree test fails and apache segfaults,
> > even with the latest cvs.
> > apache 2.0.37-dev
> > modperl 1.99_02-dev
> > win2k
> > perl 561
>
> That's wierd - I have the same set-up, except using WinXP, and
> this test passes ... What happens if you remove t/conf/httpd.conf
> (so as to regenerate it) before running the tests - are things
> any different?
>
> best regards,
> randy
>

alas no. things are the same.
error message is "memory cant be read" from perl56.dll
here is a complete report of first test in each directory that fails and
produces segfault (with perl t/test dirtest) :

dirtest=api:
api/access :ok
api/aplog : apache segfault

dirtest=apr
apr/base34 :ok
apr/constants : ok
apr/date apache segfault

dirtest=apache
apache/cgihandler : ok
apache/compat: ok
apache/compat2:ok
apache/conftree : apache segfault

dirtest=directive
directive/env failed 1-3, 4 ok
directive/prelmodule : ok
directive/perlrequire : ok
directive/setupenv : apache segfault

dirtest=filter
all tests succesfull

dirtest=hooks
hooks/access : ok
hooks/authen : ok 2/4 and 3 segfault

dirtest=modperl
modperl/dirconfig : failed tests 6-12 failed 7/12 tests (this reminds me my
previous post about dir_config not working) and apache segfaults

dirtest=protocol
protocol/echo ok
protocol/filter ok
protocol/eliza skipped

dirtest=module
modules/cgi ok 2/5 and apache segfaults...

it would be good if there was a possibility to build modperl2 debug on
win32...
personnaly I would love to be able to report bugs with complete source
backtrace
and all that stuff required to make it funny to track bugs !

best regards
pascal






Reply via email to