[In the future please don't reply to some thread when starting a new topic,
but post a new email. thank you!]
Bobber Cheng wrote:
Hi,
Apache(2.0.48) with perl_mod(1.99_10) got a Segmentation fault when i
access a perl script from apache. I use perl-5.8.2 built from source
without thread-suppor
Stas Bekman wrote:
>
> How about this (yet another) idea. Snapshot the OpCode tree before and after
> running the sections (or PerlLoadModule). Then traverse both OpCode
> trees and somehow rip off the differences and transplant them into the newly
> perl_clone()'d interpreters. We prefer to s
Rafael Garcia-Suarez wrote:
Stas Bekman wrote:
How about this (yet another) idea. Snapshot the OpCode tree before and after
running the sections (or PerlLoadModule). Then traverse both OpCode
trees and somehow rip off the differences and transplant them into the newly
perl_clone()'d interprete
Stas Bekman wrote:
>
> I'm not talking about mod_perl internals, just talking about amputating a
> chunk of the Optree from one interpreter and replanting it into another
> interpreter (not perl_cloned one).
You need to explain to me what those interpreters are. IIUC from your
remark below the
Rafael Garcia-Suarez wrote:
Stas Bekman wrote:
I'm not talking about mod_perl internals, just talking about amputating a
chunk of the Optree from one interpreter and replanting it into another
interpreter (not perl_cloned one).
You need to explain to me what those interpreters are. IIUC from
Geoffrey Young wrote:
>
> the problem with this, though, is that we don't really want a clean
> interpreter, we want an _almost_ clean one - one with only the data we know
> is important (like the globals set within the section). so, if we
> could copy the relevant data from the first interpr
Rafael Garcia-Suarez wrote:
Geoffrey Young wrote:
the problem with this, though, is that we don't really want a clean
interpreter, we want an _almost_ clean one - one with only the data we know
is important (like the globals set within the section). so, if we
could copy the relevant data fr
[EMAIL PROTECTED] wrote:
geoff 2003/11/12 08:24:28
Modified:.RELEASE
Log:
use relative links
add chmod routines
move old releases to old - don't remove entirely
add www.apache.org/dist/perl placeholder
Revision ChangesPath
1.8 +25 -10modperl-2.0/
-% ln -sf /www/perl.apache.org/dist/mod_perl-1.99_12.tar.gz \
- /www/perl.apache.org/dist/mod_perl-2.0-current.tar.gz
+% ln -sf mod_perl-1.99_12.tar.gz mod_perl-2.0-current.tar.gz
% tar -xzvf mod_perl-1.99_12.tar.gz
% rm /www/perl.apache.org/dist/mod_perl-2.0-curre
Geoffrey Young wrote:
-% ln -sf /www/perl.apache.org/dist/mod_perl-1.99_12.tar.gz \
- /www/perl.apache.org/dist/mod_perl-2.0-current.tar.gz
+% ln -sf mod_perl-1.99_12.tar.gz mod_perl-2.0-current.tar.gz
% tar -xzvf mod_perl-1.99_12.tar.gz
% rm /www/perl.apache.org/d
I'm not sure who is right then, so you'll have to take it up with him.
Interesting. Do you have that email, so that I can followup on it?
done.
also, note that I followed his instruction and generated relative symlinks
(in the form I wrote in the RELEASE doc) in both dist/ directories - so, t
I guess I just was not lucky enough.
I upgraded my env to
Apache 2.0.48, mod_perl 1.99_11, perl 5.8.2, gcc 3.3 on solaris 2.8.
I'm still having the same problem. the server just cannot be started.
I had successfully built an older version of mod_perl with gcc 2.95.2;
however, I have no luck with g
I have a large form (1000+ form elements) which uses method="POST". Only
the first 429 elements/parameters are passed to my mod_perl application.
The odd thing is, it only happens with Mozilla Firebird (Win32), and not
MSIE. I originally thought this was a browser issue, but when I tried
the sa
Please disregard, the latest build (mod_perl-1.99_11) fixed the problem.
Cheers,
y
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[EMAIL PROTECTED] wrote:
I guess I just was not lucky enough.
I upgraded my env to
Apache 2.0.48, mod_perl 1.99_11, perl 5.8.2, gcc 3.3 on solaris 2.8.
I'm still having the same problem. the server just cannot be started.
I had successfully built an older version of mod_perl with gcc 2.95.2;
howeve
Geoffrey Young wrote:
Rafael Garcia-Suarez wrote:
Geoffrey Young wrote:
the problem with this, though, is that we don't really want a clean
interpreter, we want an _almost_ clean one - one with only the data
we know is important (like the globals set within the
section). so, if we could co
ActiveState just released version 807, which is based on the
perl-5.8.1 sources with some 5.8.2 enhancements. The sources
they use don't include the hash randomization stuff of
5.8.1/5.8.2 (so that builds using 807 will be binary
compatible with pre-807 builds), and they define
NO_HASH_SEED in the
17 matches
Mail list logo
