Crash occurs during LDAP Search



15 years ago
15 years ago


(Reporter: Bernard R Heroux, Assigned: mcs)


Firefox Tracking Flags

(Not tracked)




15 years ago
User-Agent:       Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0; (R1 1.1); .NET CLR 1.0.3705)
Build Identifier:

The following is a core dump that occured during an LDAP Crash.  
Any assistance in understanding this core would be much appreciated.  It does
not happen every time but does happen frequently.  I have several core files. 
Here is one of them.

  0x171dce in remove_block_from_free_list ()
#1  0x171b56 in _free ()
#2  0x171a6a in free ()
#3  0x9ac0d in nslberi_free (ptr=0x471868) at io.c:1184
#4  0x9a510 in ber_sockbuf_free (p=0x471868) at io.c:657
#5  0x94651 in nsldapi_free_connection (ld=0x45bc0c, lc=0x45b5d4, force=0, 
    unbind=1) at request.c:545
#6  0x946f1 in nsldapi_free_request (ld=0x45bc0c, lr=0x45b4dc, free_conn=1)
    at request.c:687
#7  0x946d5 in nsldapi_free_request (ld=0x45bc0c, lr=0x45b37c, free_conn=1)
    at request.c:682
#8  0x92b2f in read1msg (ld=0x45bc0c, msgid=2, all=1, sb=0x471868, 
    lc=0x45b5d4, result=0x7fef8db8) at result.c:568
#9  0x926b1 in wait4msg (ld=0x45bc0c, msgid=2, all=1, unlock_permitted=1, 
    timeout=0x4318cc, result=0x7fef8db8) at result.c:307
#10 0x922ef in nsldapi_result_nolock (ld=0x45bc0c, msgid=2, all=1, 
    unlock_permitted=1, timeout=0x4318cc, result=0x7fef8db8) at result.c:173
#11 0x9217a in ldap_result (ld=0x45bc0c, msgid=2, all=1, timeout=0x4318cc, 
    result=0x7fef8db8) at result.c:88
#12 0x9113b in ldap_search_ext_s (ld=0x45bc0c, 
    base=0x45b324 "dc=nile2,dc=rmst,dc=mc,dc=xerox,dc=com", scope=2, 
    filter=0x431cff "(uid=nile017)", attrs=0x0, attrsonly=0, serverctrls=0x0, 
    clientctrls=0x0, timeoutp=0x4318cc, sizelimit=25, res=0x7fef8db8)
---Type <return> to continue, or q <return> to quit---
    at search.c:886
#13 0x88080 in ldap_search_request (callbackFn=0x10e14)
    at aba_ldap_interface.c:1270

Reproducible: Sometimes

Steps to Reproduce:
1. Authenticate to a Network Server (this is what goes on in the system before 
ldap search)
2. Perform LDAP Search on authenticated users name

Actual Results:  
crash as listed in details

Expected Results:  
not crashed.

Comment 1

15 years ago
I would like to determine if this is a bug in the LDAP libraries or a Mozilla
client bug.

Please provide information about platform, which client build you are using, and
so on.

Comment 2

15 years ago
I would very much like to talk to you about this problem.

I will update the log accordingly.  But am also not certain what the root cause 
to this is,
library or client.  However, I would expect the library to not crash, to handle 
this scenario better.

I have noticed this crash with Exchange 2000 LDAP server configuration. I am 
the Mozilla code as an LDAP client to connect to the Exchange 2000 LDAP 

I am running on a flavor of UNIX called LynxOS. 

Is there a phone number I can reach you at to discuss this?

Thanks in advance,

Comment 3

15 years ago
As we discussed on the telephone, my best guess is that a double-free or use of
freed memory is occurring.

Comment 4

15 years ago
I can't remember where we left off on this bug... any more information to share?

Comment 5

15 years ago

I took some of the changes that Mark Smith sent me and it appears to have 
resolved the problem. The specific code dealt with the freeing of child nodes 
before the parent. 

Thanks for all the help.


Comment 6

15 years ago
Resolving as WorksForMe (because this had already been fixed in newer LDAP code
than was being used).
Last Resolved: 15 years ago
Resolution: --- → WORKSFORME

Comment 7

15 years ago
Spam for bug 129472
QA Contact: nobody → nobody
You need to log in before you can comment on or make changes to this bug.