[Date Prev][Date Next]
Re: (ITS#5163) slapd segfaults when running as proxy-caching server
>> I would have expected the problem to show up more frequently, if I
>> just need to use a filter that will result in attributes being cached.
> well, the issue you seem to see is quite clear; probably it doesn't show
> up that frequently because by chance there happens to be a NULL somewhere
> along the path before a SIGSEGV is triggered. Running slapd under
> valgrind or similar memory debuggers would probably track it much quicker.
> And there might be more; only, this is for sure a bug.
OK, yes, I see what you're saying. I'll patch and report back.