Hi Philippe & List

(Sorry for not looking in the archives good enough!)

On 5/24/05, Philippe M. Chiasson <[EMAIL PROTECTED]> wrote:
> Flavio Curti wrote:
> > I have a problem running mod_perl-2.0.0 (and the latest devel snapshot too):
> It would be quite helpfull if you could just get me:
> (gdb) print *dconf
> (gdb) print *(dconf->sec_file)
[Switching to Thread -1212529568 (LWP 16147)]
0xb75a86dc in ap_pcw_walk_files_config (pconf=0x80c20a8, s=0x80c8018, 
    dconf=0x80fe4a8, modp=0xb75bb500, 
    dir_cb=0xb75a82d0 <modperl_hash_handlers_dir>, data=0x0)
    at modperl_pcw.c:67
67          ap_conf_vector_t **dirs = (ap_conf_vector_t 
**)dconf->sec_file->elts;
(gdb) print *dconf
$1 = {d = 0x0, d_components = 0, opts = 31 '\037', opts_add = 0 '\0', 
  opts_remove = 0 '\0', override = 63 '?', ap_default_type = 0x0, 
  satisfy = 0x80fe528, ap_auth_type = 0x0, ap_auth_name = 0x0, 
  ap_requires = 0x0, response_code_strings = 0x0, hostname_lookups = 0, 
  do_rfc1413 = -2, content_md5 = -2, use_canonical_name = 3, d_is_fnmatch = 0, 
  add_default_charset = 2, add_default_charset_name = 0x80a76d7 "iso-8859-1", 
  limit_cpu = 0x0, limit_mem = 0x0, limit_nproc = 0x0, limit_req_body = -1, 
  limit_xml_body = -1, server_signature = 4294967295, loglevel = 2, 
  sec_file = 0x0, r = 0x80fe628, mime_type = 0x0, handler = 0x0, 
  output_filters = 0x0, input_filters = 0x0, accept_path_info = 0, 
  ct_output_filters = 0x3, etag_bits = 0, etag_add = 0, etag_remove = 0, 
  enable_mmap = 0, enable_sendfile = 0, allow_encoded_slashes = 0}
(gdb) print *(dconf->sec_file)
Cannot access memory at address 0x0
(gdb) 

> > In order to isolate the problem further I changed line 118 of modperl_pcw.c 
> > from
> >   if (dir_cb) {
> > to
> >   if (dir_cb && 0) {
> > and mod-perl2 started working! So there seems to be a problem with
> > reading configuration files/directories somehow.
> Do you mean that the test suite passed _all_ it's tests or that the server
> simply started up ? Because that patch would disable quite a few important
> things.

Well, yeah it simply didn't segfault anymore. From running make test
it seemed that many
tests failed so I didn't bother running it through.
 
> Can you also try this patch ?
Okay, I applied this patch to the 2.0 Version. Apache no longer
segfaults but 201 out of 229 test scripts fail:
Failed 201/229 test scripts, 12.23% okay. 377/684 subtests failed, 44.88% okay.
Judging from the error_log it's because the apache-childs segfault. I
have attached with gdb to the running test apache, and when accessing
http://localhost:8531/TestUser__rewrite_real the child segfaults:

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread -1212529568 (LWP 23182)]
0xb759acbf in modperl_hook_create_request (r=0x959e028) at mod_perl.c:718
718         MP_dRCFG;
(gdb) bt
#0  0xb759acbf in modperl_hook_create_request (r=0x959e028) at mod_perl.c:718
#1  0x0809ad55 in ap_run_create_request ()
#2  0x08092491 in ap_read_request ()
#3  0x0806cb58 in _start ()
#4  0x095980e8 in ?? ()
#5  0x00000003 in ?? ()
#6  0x00000000 in ?? ()
#7  0xb75b3ec0 in modperl_process_connection_handler (c=0x0)
    at modperl_hooks.c:17
#8  0x0808da55 in ap_run_process_connection ()
#9  0x08080e94 in ap_graceful_stop_signalled ()
#10 0x08080fe7 in ap_graceful_stop_signalled ()
#11 0x08081279 in ap_graceful_stop_signalled ()
#12 0x08081965 in ap_mpm_run ()
#13 0x08087efd in main ()

If you need anything else just tell me. If a verbose test-report is
needed just tell me which test.

Thank you very much for your help and kind regards

Flavio

-- 
http://no-way.org/~fcu/

Reply via email to