ry 06, 2004 1:13 PM
> To: Hyoung-Kee Choi
> Cc: [EMAIL PROTECTED]
> Subject: Re: [mp2] mod_perl 2.0 "make test" generated a coredump
>
>
> Hyoung-Kee Choi wrote:
> > I am reposing the following bug report again with a hope that I
> would get an
> > answe
I am reposing the following bug report again with a hope that I would get an
answer soon.
> -Original Message-
> From: Hyoung-Kee Choi [mailto:[EMAIL PROTECTED]
> Sent: Friday, December 26, 2003 11:01 AM
> To: [EMAIL PROTECTED]
> Subject: [mp2] mod_perl 2.0 "ma
My system has httpd 2.0 compiled with
"-D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64" . "make test" of mod_perl has
genearted a coredump with the following backtrace.
--
(gdb) backtrace
#0 0x405c1bec in ap_pcw_walk_files_config (pconf=0x809d078, s=0x80b7230,
dcon
My system has httpd 2.0 compiled with
"-D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64" . "make test" of mod_perl has
genearted a coredump with the following backtrace.
--
(gdb) backtrace
#0 0x405c1bec in ap_pcw_walk_files_config (pconf=0x809d078, s=0x80b7230,
dcon
n __libc_start_main
() from /lib/libc.so.6(gdb) print dconf$1 = (core_dir_config *)
0x80b7908(gdb) display dconf (gdb) print dconf->sec_file$2 =
(apr_array_header_t *) 0x0
---
but, mod_perl works fine with
httpd w/o largefile support.
Folks,
mod_perl failed to test and generated a strange coredump. The following of
the coredump revealed that the dump was occurred because of the null value
in dconf->sec_files in ap_pcw_walk_files_config in modperl_pcw.c. Any
suggestions to solve this problem?
--
Reporting bugs: http
