My compiler didn't catch that missing cast. What version of gcc are you
using ?
[EMAIL PROTECTED] /home/pgollucci 1>gcc -v
Using built-in specs.
Configured with: FreeBSD/i386 system compiler
Thread model: posix
gcc version 3.4.4 [FreeBSD] 20050518
---
Philip M. Gollucci wrote:
>
>> Philip M. Gollucci wrote:
>>
You will only get the Seg fault or Bus error when a process comes round
for recycling.
>>
>>
>> This is basically caused by the assumption that %ENV will be tied, and
>> local %ENV
>> breaks that assumption ;-S
>>
>> The followi
Philip M. Gollucci wrote:
You will only get the Seg fault or Bus error when a process comes round
for recycling.
This is basically caused by the assumption that %ENV will be tied, and local
%ENV
breaks that assumption ;-S
The following patch fixes this problem for me:
[patch snipped]
Some
Philip M. Gollucci wrote:
>> You will only get the Seg fault or Bus error when a process comes round
>> for recycling.
This is basically caused by the assumption that %ENV will be tied, and local
%ENV
breaks that assumption ;-S
The following patch fixes this problem for me:
Index: src/modules/p
an't fix it.
Program received signal SIGSEGV, Segmentation fault.
0xfe971904 in modperl_env_request_tie (r=0x793a08) at modperl_env.c:355
355 EnvMgObj = (char *)r;
(gdb) bt
#0 0xfe971904 in modperl_env_request_tie (r=0x793a08) at modperl_env.c:355
#1 0xfe95957c in modperl_response_handler_cgi
"show warranty" for details.
This GDB was configured as "sparc-sun-solaris2.9"...
(gdb) run -X -f /usr/local/wasm_apache/bin/httpd -X -f
/usr/local/wasm_apache/conf/httpd.conf -k start -DSSL -X
Starting program: /opt/local/apache_2.0.49_prefork/bin/httpd -X -f
/usr/local/wa
matter
to be able to understand your problem. You don't have a problem to start
the modperl > test suite, do you?
In fact any attempt to start apache with mod_perl (including the one in the
test suite) causes a segmentation fault.
OK. Any chance you can try building perl with ithreads and the
ki. You need to give us more matter to be
> able to understand your problem. You don't have a problem to start the modperl >
> test suite, do you?
In fact any attempt to start apache with mod_perl (including the one in the test
suite) causes a segmentation fault.
> If that'
Kiki wrote:
I couldn't find any references to a possible cause of the segmentation
fault. Does mod_perl 1.99_13 solve this problem?
We are not aware of this problem, Kiki. You need to give us more matter to be
able to understand your problem. You don't have a problem to start the mod
I couldn't find any references to a possible cause of the segmentation fault. Does
mod_perl 1.99_13 solve this problem?
Anyway, here's the bug report:
1. Problem Description:
Segmentation fault when starting Apache2 with mod_perl
2. Used Components and their Configuration:
**
Stas Bekman wrote:
Bobber Cheng wrote:
[...]
Well, that renders the check, whether the file was already opened,
useless, in which case we should just:
rc = apr_file_open(...)
no matter what. I've now posted a question to the apr list asking how to
verify whether finfo contains a valid filehand
Bobber Cheng wrote:
(gdb) p r->filename
$1 = 0x81a1818 "/usr/local/lxr/source"
(gdb) p r->finfo
$2 = {pool = 0x819fe80, valid = 7598448, protection = 1877,
filetype = APR_REG, user = 48, group = 48, inode = 410325, device = 774,
nlink = 1, size = 7123, csize = 1077577583, atime = 1068909622
ote:
>Bobber Cheng wrote:
>> Hi, Stas:
>>
>> thx ur quck reply. The problem remained although i applied ur patch to last cvs
>> mod_per and run on last cvs apache2.
>>
>> perl -v
>> This is perl, v5.8.2 built for i686-linux
>> ./httpd -v
>>
change where Segmentation fault raise, here is the gdb output:
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 16384 (LWP 8102)]
0x40174670 in apr_file_read (thefile=0x1, buf=0x824f6f0, nbytes=0xb468)
at readwrite.c:79
79 if (thefile->buffered) {
(
Segmentation fault raise, here is the gdb output:
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 16384 (LWP 8102)]
0x40174670 in apr_file_read (thefile=0x1, buf=0x824f6f0, nbytes=0xb468)
at readwrite.c:79
79 if (thefile->buffered) {
(gdb) backtrace
[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 t
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-support. perl_mod is complied by perl "Makefile.PL MP_INST_APACHE2=1 MP_DEBUG=1 MP_AP_PREFIX=/usr/local/apache2".
GNU gdb Red
On Wed, 11 Sep 2002, Dave Smith wrote:
> > does 'make test' pass for you?
answer to this question?
if yes, can you provide your configuration. i can't see anything abnormal
with the trace output.
-
To unsubscribe, e-mail:
Doug MacEachern said:
> On Fri, 6 Sep 2002, Dave Smith wrote:
>
>> I'm using mod_perl-2.0 (cvs version).
>> I did a cvs update this morning. Here's the trace:
>
> stacktrace looks like the perl interpreter is not being destructed. i've
> seen this before, but was due to a bug that has been since
On Fri, 6 Sep 2002, Dave Smith wrote:
> I'm using mod_perl-2.0 (cvs version).
> I did a cvs update this morning. Here's the trace:
stacktrace looks like the perl interpreter is not being destructed.
i've seen this before, but was due to a bug that has been since fixed long
ago. not seeing the
Doug MacEachern said:
> On Thu, 29 Aug 2002, Dave Smith wrote:
>
>> (Not sure if this belong on the httpd list or this one... ?)
>
> this one.
>
>>
>> -8<-- Start Bug Report 8<--
>
> hmm, we don't include $mod_perl::VERSION in this report?
>
> what version
On Thu, 29 Aug 2002, Dave Smith wrote:
> (Not sure if this belong on the httpd list or this one... ?)
this one.
>
> -8<-- Start Bug Report 8<--
hmm, we don't include $mod_perl::VERSION in this report?
what version are you using? if from-cvs, can you
Dave Smith wrote:
> OK, I rebuilt perl with -Uuselargefiles, then rebuilt mod_perl.
>
> Stills gives a core dump, but looks a little differnt...
>
> #0 0x403a9793 in Perl_require_pv (pv=0x814a498
> "/data/httpd/perl/startup2.pl") at perl.c:2197
> 2197 PUSHSTACKi(PERLSI_REQUIRE);
> (gdb) wh
OK, I rebuilt perl with -Uuselargefiles, then rebuilt mod_perl.
Stills gives a core dump, but looks a little differnt...
#0 0x403a9793 in Perl_require_pv (pv=0x814a498
"/data/httpd/perl/startup2.pl") at perl.c:2197
2197PUSHSTACKi(PERLSI_REQUIRE);
(gdb) where
#0 0x403a9793 in Perl_requi
Dave Smith wrote:
> (gdb) where
> #0 0x403965f6 in Perl_require_pv () from
> /opt/local/apache2/modules/mod_perl.so
this is weird, modperl_require_file() calls require_pv(pv), which seems
to be just right in the frame #1. but it never gets passed to require_pv().
> #1 0x4038803e in modperl_re
1.
>> Problem Description:
>>
>> Apache 2.0 starts w/out errors and immediately dies.
>>
>> $ ./httpd -X -e debug
>> [debug] mod_so.c(290): loaded module php4_module
>> [debug] mod_so.c(290): loaded module perl_module
>> Segmentation fau
-e debug
> [debug] mod_so.c(290): loaded module php4_module
> [debug] mod_so.c(290): loaded module perl_module
> Segmentation fault
[...]
> 3. This is the core dump trace: (if you get a core dump):
>
> no core dump!
The report is useless without the back trace,
[debug] mod_so.c(290): loaded module perl_module
Segmentation fault
$
2. Used Components and their Configuration:
*** using lib/Apache/BuildConfig.pm
*** Makefile.PL options:
MP_AP_PREFIX=> /opt/local/apache2
MP_GENERATE_XS => 1
MP_INST_APACHE2 => 1
MP_LIBNAME
28 matches
Mail list logo
