On Wed, Dec 30, 1998, [EMAIL PROTECTED] wrote:
Fixed: recompiled SSLeay with gcc-2.7.2, -O2 -g
(previously: without -O2 -g)
will check out other combinations tomorrow ...
That's interesting. Then either the compiler was broken or at least SSLeay
used some stuff which is slightly broken on
On Tue, Dec 29, 1998, [EMAIL PROTECTED] wrote:
sorry for mostly sleeping concerning mod_ssl over the last few weeks
(I followed up to 2.1.0 but not afterwards).
I just tested mod_ssl DSO support with Solaris 2.5.1, gcc-2.7.2:
(tested with 2.1.0, 2.1.1 and 2.1.4)
Everything works fine
Hi,
UID 0 based processes? Perhaps then you have to run it on ports 8080/8443
temporarily as a regular user to get the core. Without the coredump and a
backtrace it's hard to find the location of the SIGSEGV.
Thanks for the hint, Ralf.
Meanwhile I got some closer and got at least a
Fixed: recompiled SSLeay with gcc-2.7.2, -O2 -g
(previously: without -O2 -g)
will check out other combinations tomorrow ...
Hi,
UID 0 based processes? Perhaps then you have to run it on ports 8080/84=
43
temporarily as a regular user to get the core. Without the coredump and=
a
Hi,
sorry for mostly sleeping concerning mod_ssl over the last few weeks
(I followed up to 2.1.0 but not afterwards).
I just tested mod_ssl DSO support with Solaris 2.5.1, gcc-2.7.2:
(tested with 2.1.0, 2.1.1 and 2.1.4)
Everything works fine until the first restart (SIGHUP or SIGUSR1) to
the
