On Wed, Sep 05, 2001 at 12:20:04AM +0800, Stas Bekman wrote:
> On Sat, 1 Sep 2001, Philippe M . Chiasson wrote:
>
> > The following patch makes sure that MP_APXS is an absolute path. If you used
> > MP_APXS=../deps/httpd/bin/apxs it would make a bunch of things fail ;-)
> >
> > And there was also a very small patch to Apache-Test that didn't include the
> > right package.
> >
> > Note: Right now, with latest httpd & perl, I get a segfault in Perl_re_dup
>
> > #0 0x4030a3d3 in Perl_re_dup (my_perl=0x83c2828, r=0x1b, param=0x81722b8) at
>sv.c:8365
> > #1 0x4030f975 in perl_clone (proto_perl=0x8128ba8, flags=0) at sv.c:9787
> > #2 0x40276a99 in modperl_interp_new (p=0x80aeea4, mip=0x80fb41c, perl=0x8128ba8)
>at modperl_interp.c:55
> > #3 0x40276d26 in interp_pool_grow (tipool=0x80fb434, data=0x80fb41c) at
>modperl_interp.c:166
> > #4 0x4027751a in modperl_tipool_init (tipool=0x80fb434) at modperl_tipool.c:170
> > #5 0x402761d9 in modperl_init_clones (s=0x80b049c, p=0x80aeea4) at mod_perl.c:218
> > #6 0x402763b6 in modperl_hook_post_config (pconf=0x80aeea4, plog=0x80e1034,
>ptemp=0x80e3044, s=0x80b049c) at mod_perl.c:298
> > #7 0x0807bd2e in ap_run_post_config (pconf=0x80aeea4, plog=0x80e1034,
>ptemp=0x80e3044, s=0x80b049c) at config.c:124
> > #8 0x080802a1 in main (argc=7, argv=0xbffff614) at main.c:400
> > #9 0x40115177 in __libc_start_main (main=0x807fe74 <main>, argc=7,
>ubp_av=0xbffff614, init=0x805c684 <_init>, fini=0x8095f80 <_fini>,
>rtld_fini=0x4000e184 <_dl_fini>, stack_end=0xbffff60c) at
>../sysdeps/generic/libc-start.c:129
> >
> > Seems like the regexp passed (r) is completely bogus (0x1b). Anybody seeing this
>too?
>
> I don't see that.
I tracked it down a little bit more. ;-(
This is with :
perl-devel(11927)
httpd2(cvs as of now) MPM=threaded
With the forking MPM everything goes well...
Apparently, something broke with perl_clone ;-(
Guess I'll switch to forked MPM for now.
>
> when do you get this? At the startup? My perl is a few months old, I still
> get some tests failed with the last minute build. I'm not sure whether
> it's a good idea to install anyway. Do you get your 'make test' clean?
> That's what I get:
>
> Failed 16 test scripts out of 576, 97.22% okay.
> ### Since not all tests were successful, you may want to run some
> ### of them individually and examine any diagnostic messages they
> ### produce. See the INSTALL document's section on "make test".
> ### If you are testing the compiler, then ignore this message
> ### and run
> ### ./perl harness
> ### in the directory ./t.
> ###
> ### Since most tests were successful, you have a good chance to
> ### get information with better granularity by running
> ### ./perl harness
> ### in directory ./t.
>
>
> _____________________________________________________________________
> Stas Bekman JAm_pH -- Just Another mod_perl Hacker
> http://stason.org/ mod_perl Guide http://perl.apache.org/guide
> mailto:[EMAIL PROTECTED] http://apachetoday.com http://eXtropia.com/
> http://singlesheaven.com http://perl.apache.org http://perlmonth.com/
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
--
Philippe M. Chiasson <[EMAIL PROTECTED]>
Extropia's Resident System Guru
http://www.eXtropia.com/
When you rewrite a compiler from scratch, you sometimes fix
things you didn't know were broken.
-- Larry Wall
perl -e '$$=\${gozer};{$_=unpack(P26,pack(L,$$));/^Just Another Perl
Hacker!\n$/&&print||$$++&&redo}'
PGP signature
