Philippe M. Chiasson wrote:
If we encounter core dumps with the static build, this small fix
recommends the right
gdb command to run, since the httpd binary is actually a libtool shell
script wrapper
sweet, but:
- it's a huge waste of time to parse the script again and again, instead
do it once,
If we encounter core dumps with the static build, this small fix
recommends the right
gdb command to run, since the httpd binary is actually a libtool shell
script wrapper
Index: Apache-Test/lib/Apache/TestRun.pm
===
RCS file: /home/
Philippe M. Chiasson wrote:
It's not your tests that are at fault, Stas. Something
else is broken, and that commit brought it out. As
I said earlier, I've been having segfault problems with mp2 for a few
days now (Tuesday it was the send_fd
tests, which I wrote about on [EMAIL PROTECTED])
why c
Matthew Hodgson wrote:
Stas Bekman wrote:
Matthew, please try the current cvs, Philippe has been working hard
on improving the static build since _16 was released.
http://perl.apache.org/download/source.html#Development_mod_perl_2_0_Source_Distribution
Okay, my previous build using latest mod_pe
t/TEST t/filter/out_str_reverse.t t/apr/table.t t/filter/out_str_req_mix.t
t/api/sub_request.t t/api/aplog.t t/modperl/merge.t
end ups with a segfault (but not always):
#0 0x080eaed2 in ap_save_brigade (f=0x9540b18, saveto=0x9540b58,
b=0xbfffeb84, p=0x9557f40) at util_filter.c:539
---Type t
David Wheeler wrote:
Hi All,
I'm finally getting 'round to installing Apache 2 and wanted to install
mod_perl while I was at it (since there is increasing interest in
getting Bricolage running on mod_perl 2!). I've been using the worker
MPM on Ask's advice, but looking at the docs, it appears th
Philippe M. Chiasson wrote:
The following patch takes $r->log_reason out of compat and into
the mainline API (doc patch to follow)
+1
I'm not sure if we should check where log_reason was previously used in
mp1 core functions and probably put it back to use? like registry, status
and other modules
The following patch takes $r->log_reason out of compat and into
the mainline API (doc patch to follow)
Index: Changes
===
RCS file: /home/cvs/modperl-2.0/Changes,v
retrieving revision 1.496
diff -u -I$Id -r1.496 Changes
--- Changes 2
Stas Bekman wrote:
Joe Schaefer wrote:
Stas Bekman <[EMAIL PROTECTED]> writes:
[...]
All I did is adding some vhosts around normal tests.
It's not your tests that are at fault, Stas. Something
else is broken, and that commit brought it out. As
I said earlier, I've been having segfault problems
On Sep 24, 2004, at 1:45 PM, David Wheeler wrote:
Thanks, Vivek. Perhaps I'll ask my hosting provider for an upgrade. Is
FreeBSD 5 stable now?
FreeBSD 5.3 scheduled for October 10 is supposed to be the new "stable"
branch of FreeBSD. I have one production server running 5.2.1 right
now and it
David Wheeler wrote:
Thanks, Vivek. Perhaps I'll ask my hosting provider for an upgrade. Is
FreeBSD 5 stable now?
5.3 (the first stable release to come from the 5.x branch) will be out
real soon now, but it's not out yet. See
http://www.freebsd.org/releases/5.3R/schedule.html for details.
-gar
On Sep 24, 2004, at 10:16 AM, Vivek Khera wrote:
On FreeBSD 4 threads suck. They don't just suck, they blow too.[1]
I've never had anything but trouble with them. They are user-land
threads, so must cooperate for any kind of concurrency. I'm trying to
get Postgres to replicate using Slony-I, a
On Sep 24, 2004, at 12:55 PM, David Wheeler wrote:
And on a slightly related note, just how poorly do threads work on
FreeBSD? I'm setting up a Subversion server and would like to use
ViewCVS, but mod_python (/me throws salt over his shoulder) requires
--enable-threads. Anyone here got much expe
On Sep 24, 2004, at 9:14 AM, David Wheeler wrote:
Oh, I just saw this in the Apache 2 docs:
* If you are building on FreeBSD, be aware that threads
will
be disabled and the prefork MPM will be used by default,
as threads do not work well with Apache on FreeB
Hi All,
I'm finally getting 'round to installing Apache 2 and wanted to install
mod_perl while I was at it (since there is increasing interest in
getting Bricolage running on mod_perl 2!). I've been using the worker
MPM on Ask's advice, but looking at the docs, it appears that I either
have to
Stas Bekman <[EMAIL PROTECTED]> writes:
[...]
> trying to understand what the problem is and how to write a test for
> it and how to fix it. will keep you posted.
The problem is that the current modperl_bucket.c implementation
needs a proper setaside function. Think about it- the interpreter
on
I was building mp2 statically ( latest cvs version ) with the following :
perl Makefile.PL MP_USE_STATIC=1 MP_INST_APACHE2=1
MP_AP_PREFIX=/home/pratik/src/mp2/httpd-2.0.51 MP_MAINTAINER=1
MP_AP_CONFIGURE="--enable-maintainer-mode --enable-so --enable-rewrite
--enable-logio --enable-log-forensic"
Hi,
Am 24.09.2004 um 14:30 schrieb Joe Schaefer:
Boris Zentner <[EMAIL PROTECTED]> writes:
[...]
It makes only sense the other way around. A $apr->param('parameter');
must provide a valid object.
That's why I suggested subclassing Apache::Request,
so you can have param() do whatever you want.
Thats
Boris Zentner <[EMAIL PROTECTED]> writes:
[...]
> It makes only sense the other way around. A $apr->param('parameter');
> must provide a valid object.
That's why I suggested subclassing Apache::Request,
so you can have param() do whatever you want.
--
Joe Schaefer
-
Hi,
Am 24.09.2004 um 03:06 schrieb Joe Schaefer:
Boris Zentner <[EMAIL PROTECTED]> writes:
In my real case, I get the data from libapreq2 in raw format and my
desire is to convert some of them inplace to utf8. Then the rest of my
application can rely on libapreq's functions.
That will not work, bec
Hi,
Am 24.09.2004 um 02:37 schrieb Stas Bekman:
Boris Zentner wrote:
Hi,
Am 24.09.2004 um 01:50 schrieb Stas Bekman:
Boris Zentner wrote:
Hi,
Whenever I store something into a APR::Table I get different data
back. Even with a recent mod_perl I use
APR::Table stores plain strings. It doesn't know
21 matches
Mail list logo