8-Feb-99 12:31 you wrote:
> Khimenko Victor wrote:
>>
>> If you use libc5-based Linux then try to use built-in SDBM !
>> At least Slackware 3.6 has broken DBM :-((
> Uh oh. Yeah, definately a problem here. Slack 3.6 it is. Excuse me for
> not knowing exactly what a "SDBM" is, but I'm left at a loss. Can you
> elaborate a little on an easy procedure or docs to read?
I'm never seen Slackware 3.6 myself but there are letter in mod_ssl mailing
list:
-- cut --
> Full_Name: Bryan Mawhinney
> Version: 2.1.8-1.3.4
> OS: Slackware Linux 3.6
> Submission from: (NULL) (196.23.0.42)
> Apache with mod_ssl and SSL session cache was seg faulting on most (but not all)
> transfers, in a similar manner to that which other Linux users have described
> (eg, PR# 57, 58, 74 and 78). Disabling the session cache fixes the problem, but
> we don't want to do that.
> We compiled with -g -ggdb3 and ran as non-root on port 8443. gdb of the
> resulting core file showed that the fault occurs in memcpy, but doesn't show the
> call stack (as with PR#74). Perhaps memcpy is corrupting the stack?
> We recompiled mod_ssl and forced it to use the builtin SDBM (by renaming libdbm)
> and the seg faults have disappeared. We're happy with this solution, but
> thought this info might help you identify the problem.
-- cut --
______________________________________________________________________
Apache Interface to SSLeay (mod_ssl) www.engelschall.com/sw/mod_ssl/
Official Support Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
