Bug#476415: apache2 (SSL?) x64 segfault

2008-04-16 Thread Джонатан Вашингтон 
On 17/04/2008, Stefan Fritsch <[EMAIL PROTECTED]> wrote:
> Hi,
>
>  On Wednesday 16 April 2008, Джонатан Вашингтон wrote:
>  > Package: apache2
>  > Version: 2.2.8-3
>  >
>  > Apache2 and apache2ctl both segfault.  I believe it's related to
>
>  Please follow the instructions
>  in /usr/share/doc/apache2.2-common/README.backtrace to provide a
>  stack trace.

Installing the debug symbols made it stop crashing. (!)  But SSL still
doesn't work.. probably unrelated now though, will have to check the
config.

>  > I'm running gcc 4.2.3 (and before, with the same problem, 4.1.3),
>  > and everything's 64bit.
>
>  Does that mean you have compiled apache2 yourself?

No, thought I'd include that just in case it was relevant.  Using
debian's binaries.

>  Is the segfault new and did it work before, or have you tried for the
>  first time?

It worked until several months ago when one time I updated apache.

> Which versions of libapr1 and libaprutil1 do you have installed?

libapr1 1.2.11-1
libaprutil1 1.2.12+dfsg-3

>
>  Cheers,
>
> Stefan
>

-- 
Jonathan

Bug#476415: apache2 (SSL?) x64 segfault

2008-04-16 Thread Джонатан Вашингтон 
Package: apache2
Version: 2.2.8-3

Apache2 and apache2ctl both segfault.  I believe it's related to SSL,
since apache.org's issues system appears to have a number of similar
bugs, and also because apache actually runs, but the SSL vhost I had
set up before doesn't run now.

# apache2ctl restart
/usr/sbin/apache2ctl: line 83: 14250 Segmentation fault  $HTTPD
${APACHE_ARGUMENTS} -t 2>/dev/null
Syntax OK
/usr/sbin/apache2ctl: line 83: 14251 Segmentation fault  $HTTPD
${APACHE_ARGUMENTS} -t

# apache2 -v
Server version: Apache/2.2.8 (Debian)
Server built:   Mar 14 2008 10:46:22
Segmentation fault

I'm running gcc 4.2.3 (and before, with the same problem, 4.1.3), and
everything's 64bit.

I originally posted this to the already established bug at
https://issues.apache.org/bugzilla/show_bug.cgi?id=43317 and they told
me to report it to you guys.

Please feel free to contact me regarding this bug and I'll provide any
debugging information that I can.

-- 
Jonathan



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]