[Date Prev][Date Next]
Re: (ITS#4136) test036-meta-concurrency: line 188: 1342 Segmentation fault
> On Thu, 2005-11-03 at 09:54 +0000, email@example.com wrote:
>> firstname.lastname@example.org wrote:
>>> [On AMD64]
>>> I'm seeing different different types of errors; many occur in the
>>> targets of the slapd-meta database; valgrind reports:
>>> I have no clue right now; I suspect something related to the connection
>>> handling yet, as that portion of code has been heavily changed recently.
>> I agree it's most likely to be related to the connection handling.
>> However, on my tests it is the slapd-meta process that crashes. I'll try
>> it under valgrind and see if that changes things.
> I also note that most of the invalid frees occur when slap_sl_free() is
> used, indicating that likely the context that is passed is invalid.
I haven't seen that. But re: this crash, I see that slapd #1 SEGVs
because the op it is processing has already been placed on the free list
by slap_op_free(). Looking in slapd.1.log I would guess the op got
abandoned because there is a DISCONNECT message due to bad decoding:
connection_close: deferring conn=3 sd=17
<= send_search_entry: conn 3 exit.
DISCONNECT tag=120 err=2 text=decoding error
DISCONNECT tag=120 err=2 text=error decoding filter
send_ldap_result: conn=3 op=5 p=3
send_ldap_result: err=0 matched="" text=""
send_ldap_response: msgid=6 tag=101 err=0
<= ldap_bv2dn(ou=people,dc=example,dc=com)=0 Success
I'll see what I can do about fixing this. I guess an Abandon test ought
to be able to reproduce the problem.
-- Howard Chu
Chief Architect, Symas Corp. http://www.symas.com
Director, Highland Sun http://highlandsun.com/hyc
OpenLDAP Core Team http://www.openldap.org/project/