> ALso, Marc, I'd suggest to rethink your coding techniques. Instead of using
> globals you should probably encapsulate all the data that you want to pass
> around into a single object and and pass it around, or using a Singleton
> object. Globals are not the best way to go in majority of cases.
Joe Schaefer wrote:
Stas Bekman <[EMAIL PROTECTED]> writes:
[...]
It seems that your global $GlobalS var contains a reference to an
Apache::Request table, but A-R object is not global, so when the scope
of the handler is exited A-R object gets destroyed, leaving $GlobalS
containting a pointer to
Marc Slagle wrote:
I don't have a test to reproduce the segfault, so I'm just shooting in the
dark based on the core trace that you've kindly provided. Please revert the
previous patch and try the new one:
We tried the new patch, but can still get the segfault. We wrote 3
modules that can repro
Stas Bekman wrote:
Marc Slagle wrote:
[...]
If you need any more information, please let us know.
I went through the pain of installing all these prerequisited just to
run your handlers, but it works just fine for me. I've tried to match
the perl-5.8.0 build and the only difference I think is t
Marc Slagle wrote:
[...]
If you need any more information, please let us know.
I went through the pain of installing all these prerequisited just to run your
handlers, but it works just fine for me. I've tried to match the perl-5.8.0
build and the only difference I think is that I used the latest
> I don't have a test to reproduce the segfault, so I'm just shooting in the
> dark based on the core trace that you've kindly provided. Please revert the
> previous patch and try the new one:
One more bit of information: we were using an older version of
Apache::Request, but upgraded it to the
> I don't have a test to reproduce the segfault, so I'm just shooting in the
> dark based on the core trace that you've kindly provided. Please revert the
> previous patch and try the new one:
We tried the new patch, but can still get the segfault. We wrote 3
modules that can reproduce the segfa
Marc Slagle wrote:
[...]
Thanks for the reply. Unfortunately the patch didn't resolve the
problem. The backtrace does look somewhat different, its making some
new calls before the segfault that it wasn't before. Numbers 4-13 show
differently:
[...]
I don't have a test to reproduce the segfault,
> Please try this patch:
>
> Index: src/modules/perl/Table.xs
> ===
> RCS file: /home/cvs/modperl/src/modules/perl/Table.xs,v
> retrieving revision 1.10
> diff -u -r1.10 Table.xs
> --- src/modules/perl/Table.xs 23 May 2000 15:56:12
Marc Slagle wrote:
After serving up requests normally for some time, we get the following
line in our error_log:
[Mon Nov 10 13:44:31 2003] [notice] child pid 24121 exit signal
Segmentation fault (11)
There aren't any other entries in the error log for the requests. We
think that this is happening
After serving up requests normally for some time, we get the following
line in our error_log:
[Mon Nov 10 13:44:31 2003] [notice] child pid 24121 exit signal
Segmentation fault (11)
There aren't any other entries in the error log for the requests. We
think that this is happening during the norma
11 matches
Mail list logo
