Bug report: #0 file_dup (new_file=0xbfd296d4, old_file=0x0, p=0x80a70a8, which_dup=1) at file_io/unix/filedup.c:59 segfault

2011-03-19 Thread A. Przygienda
-8<-- Start Bug Report 8<-- 1. Problem Description: Crash gentoo apache2 start. core dump below, think tries to dup a 0 file pointer [DESCRIBE THE PROBLEM HERE] 2. Used Components and their Configuration: *** mod_perl version 2.04 *** using /u

Re: Bug report: #0 file_dup (new_file=0xbfd296d4, old_file=0x0, p=0x80a70a8, which_dup=1) at file_io/unix/filedup.c:59 segfault

2011-03-19 Thread Fred Moyer
Have you tried 2.0.5? On Sat, Mar 19, 2011 at 9:15 AM, A. Przygienda wrote: > -8<-- Start Bug Report 8<-- > 1. Problem Description: > >  Crash gentoo apache2 start. core dump below, think tries to dup >  a 0 file pointer > > >  [DESCRIBE THE PROBLEM HERE] >

Re: Bug report: #0 file_dup (new_file=0xbfd296d4, old_file=0x0, p=0x80a70a8, which_dup=1) at file_io/unix/filedup.c:59 segfault

2011-03-19 Thread A. Przygienda
On 03/19/2011 06:11 PM, Fred Moyer wrote: > Have you tried 2.0.5? > nope, was on gentoo 2008 which I tried to keep but looks like I must upgrade so I check out 2011 distro now and see whether it persists -- tony > On Sat, Mar 19, 2011 at 9:15 AM, A. Przygienda wrote: >> -8<---

Re: Bug report: #0 file_dup (new_file=0xbfd296d4, old_file=0x0, p=0x80a70a8, which_dup=1) at file_io/unix/filedup.c:59 segfault

2011-05-05 Thread A. Przygienda
Same problem on 2.0.5 and gentoo 2010 That's how I run it r -D SSL -D SSL_DEFAULT_VHOST -D DEFAULT_VHOST -D INFO -D DAV -D DAV_FS -D CACHE -D MEM_CACHE -D PHP5 -D PERL_VHOST -D PYTHON -D STATUS -D PROXY -D PROXY_HTML -d /usr/lib/apache2 -f /etc/apache2/httpd.conf -E /var/log/apache2/startuperror.

Re: Bug report: #0 file_dup (new_file=0xbfd296d4, old_file=0x0, p=0x80a70a8, which_dup=1) at file_io/unix/filedup.c:59 segfault

2011-05-05 Thread A. Przygienda
After experimenting around, the reason is the global directive I use (perfectly valid) ErrorLog syslog:local6 that crashes #ifdef MP_TRACE /* httpd core open_logs handler re-opens s->error_log, which might * change, even though it still points to the same physical file * (.e.g on w