At 17:23 -0800 1/20/04, Stas Bekman wrote:
Elizabeth Mattijsen wrote:
One could argue that detached threads shouldn't be counted. But,
as I said, a detached thread is also yanked from existence as soon
as any other thread does an exit().
Hope this explains it a bit.
Thanks, Liz. But how do we de
The current CVS mp2 doesn't build on Win32 (at least) because
modperl_sv2pool (referenced in modperl.def) is an unresolved external.
The attached patch fixes this.
NOTE: I don't know if the MP_INLINE bit is needed or not, I'll leave
that to the judgement of somebody who knows what it does.
--
Elizabeth Mattijsen wrote:
At 17:23 -0800 1/20/04, Stas Bekman wrote:
Elizabeth Mattijsen wrote:
One could argue that detached threads shouldn't be counted. But, as
I said, a detached thread is also yanked from existence as soon as
any other thread does an exit().
Hope this explains it a bit.
Steve Hay wrote:
The current CVS mp2 doesn't build on Win32 (at least) because
modperl_sv2pool (referenced in modperl.def) is an unresolved external.
The attached patch fixes this.
NOTE: I don't know if the MP_INLINE bit is needed or not, I'll leave
that to the judgement of somebody who knows w
At 00:59 -0800 1/21/04, Stas Bekman wrote:
Elizabeth Mattijsen wrote:
So I think we need to have a new blocking call that will prevent
the main program/thread from exiting till all child threads are
done.
Thread::Running solves this basically.
1 while threads->running;
I looked at the implemen
Stas Bekman wrote:
>Steve, Randy, can you please try with this patch. This is against the conf
>file with:
>
>
> PerlOptions +Parent
>
>1;
>
>
>
The Good News: The patch below fixes *both* of the short conf files
that we've been playing with. Running "apache.exe -t ..." was
previousl
Elizabeth Mattijsen wrote:
I guess I could implement this in my test script using a simple
semaphore (shared variable), making sure that all callbacks pull down
that semaphore just before they are done and having the main thread
block till that semaphore gets to 0. e.g. your Running implementat
At 01:16 -0800 1/21/04, Stas Bekman wrote:
Elizabeth Mattijsen wrote:
I guess I could implement this in my test script using a simple
semaphore (shared variable), making sure that all callbacks pull
down that semaphore just before they are done and having the main
thread block till that semaphor
Steve Hay wrote:
Stas Bekman wrote:
Steve, Randy, can you please try with this patch. This is against the conf
file with:
PerlOptions +Parent
1;
The Good News: The patch below fixes *both* of the short conf files
that we've been playing with. Running "apache.exe -t ..." was
previously
Stas Bekman wrote:
>Stas Bekman wrote:
>
>
>>Another one to try (w/ and w/o last patch). As you realize I'm shooting
>>in the dark, trying to guess where the context could go wrong. Thanks.
>>
>>
>
>BTW, this one if it'll do anything should affect the PerlLoadModule faulty
>scenario and no
Steve Hay wrote:
Stas Bekman wrote:
Steve, Randy, can you please try with this patch. This is against the conf
file with:
PerlOptions +Parent
1;
The Good News: The patch below fixes *both* of the short conf files
that we've been playing with. Running "apache.exe -t ..." was
previously
Elizabeth Mattijsen wrote:
At 01:16 -0800 1/21/04, Stas Bekman wrote:
Elizabeth Mattijsen wrote:
I guess I could implement this in my test script using a simple
semaphore (shared variable), making sure that all callbacks pull
down that semaphore just before they are done and having the main
th
At 01:44 -0800 1/21/04, Stas Bekman wrote:
No, he did say that. ;-)
so no problemo then. Go for it Liz.
Eh... tuits? I won't have hardly any until at least the summer... ;-(
Liz
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
F
Stas Bekman wrote:
>Steve Hay wrote:
>
>
>>Stas Bekman wrote:
>>
>>
>>
>>
>>>Steve, Randy, can you please try with this patch. This is against the conf
>>>file with:
>>>
>>>
>>>PerlOptions +Parent
>>>
>>> 1;
>>>
>>>
>>>
>>>
>>>
>>The Good News: The patch below fixes *both* of the sh
Steve Hay wrote:
Stas Bekman wrote:
Steve Hay wrote:
Stas Bekman wrote:
Steve, Randy, can you please try with this patch. This is against the conf
file with:
PerlOptions +Parent
1;
The Good News: The patch below fixes *both* of the short conf files
that we've been playing w
Elizabeth Mattijsen wrote:
At 01:44 -0800 1/21/04, Stas Bekman wrote:
No, he did say that. ;-)
so no problemo then. Go for it Liz.
Eh... tuits? I won't have hardly any until at least the summer... ;-(
How about moving to AU, it's summer there already ;)
NZ is another great choice ;)
Am Mittwoch, 21. Januar 2004 05:41 schrieb Stas Bekman:
> but again, this is all sugar features and I won't worry about them now, as
> they can work no matter how the methods are spread across the manpages.
Right, I have a lot more ideas for the mp2doc/perldoc features. I deferred
them for now. W
Stas Bekman wrote:
>>>can't you pin-point which part of
>>>that patch causes the problem? I assume the problem is the same, right?
>>>
>>>
>>>
>>It is indeed the usual problem. I'll try produce another shortened
>>.conf file which reproduces the bug that's still lurking. Oh joy.
>>
>
Steve Hay wrote:
>>>The Bad News: The vhost test that originally didn't work way back at
>>>the start of this thread (excuse the pun) still doesn't work.
>>>
>>>
>>>
>>>
>>can't you pin-point which part of
>>that patch causes the problem? I assume the problem is the same, right?
>>
>>
Steve Hay wrote:
>Steve Hay wrote:
>
>
>
The Bad News: The vhost test that originally didn't work way back at
the start of this thread (excuse the pun) still doesn't work.
>>>can't you pin-point which part of
>>>that patch causes the proble
Stas Bekman wrote:
[...]
Moreover we do this silly (but necessary) protection and copy the whole
string into a perl sv, scared that someone will use a short-lived pool
object when allocating this variable (was my idea).
I say, let's drop that glue and write it in pure perl:
use File::Spec qw(catfi
This is just an update on the patch that I've sent long time ago, since the
older patch won't work with the current cvs. It's just the tests, so it most
likely fails just as before on win32.
--- /dev/null 1969-12-31 16:00:00.0 -0800
+++ t/vhost/basic.t 2004-01-21 15:51:20.0
Steve Hay wrote:
[...]
OK, here's another short conf file which does now break again:
=
LoadModule perl_module C:\Temp\modperl-2.0\src\modules\perl\mod_perl.so
ServerName localhost:8529
Listen 8529
ServerRoot C:/Temp/modperl-2.0/t
DocumentRoot C:/Temp/modperl-2.0/t/htdocs
LogLevel
On Wed, 21 Jan 2004 16:28:45 -0800, Stas Bekman <[EMAIL PROTECTED]> wrote:
>Steve Hay wrote:
>[...]
>BTW, if you've read my request to p5p, I don't think the perl_destruct traces
>(on the infamous error) are of any good use. Since they just tell that there
>is a problem, but they don't say where
Jan Dubois wrote:
On Wed, 21 Jan 2004 16:28:45 -0800, Stas Bekman <[EMAIL PROTECTED]> wrote:
Steve Hay wrote:
[...]
BTW, if you've read my request to p5p, I don't think the perl_destruct traces
(on the infamous error) are of any good use. Since they just tell that there
is a problem, but they d
And here are two more patches to try (all against the fresh cvs). This is
similar to one successful path that changes and restores context inside perldo
(Apache::PerlSections).
The first one adds the setting of the context inside modules
(PerlModule/PerlLoadModule) though it doesn't restore it.
On Wed, 21 Jan 2004, Stas Bekman wrote:
> And here are two more patches to try (all against the
> fresh cvs). This is similar to one successful path that
> changes and restores context inside perldo
> (Apache::PerlSections).
>
> The first one adds the setting of the context inside modules
> (PerlM
It looks like Jan's patch allows me to reproduce the problems that you see. So
if that's true, we will be all set shortly. So don't waste your time on
testing things I've asked to. I'll keep you posted. Thanks.
__
Stas Bekman
Randy Kobes wrote:
[...]
This patch wouldn't compile for me - I get the errors
cd "src/modules/perl" && NMAKE -f Makefile.modperl
[...]
Does this make sense? Or might it be a mis-applied
patch (although I did double-check it).
Yes, sorry, the usual declaration problem:
> + orig_perl = PE
Stas Bekman wrote:
It looks like Jan's patch allows me to reproduce the problems that you
see. So if that's true, we will be all set shortly. So don't waste your
time on testing things I've asked to. I'll keep you posted. Thanks.
It's so much happier when things fail ;)
Here is what happening:
30 matches
Mail list logo
