Full_Name: Olivier GERMAIN
OS: Solaris 5.10
Submission from: (NULL) (126.96.36.199)
One of our customer got a signal 6 during the execution of the ldap_abandon.
This signal occurred whereas some maintenance was doing on a firewall which is
not located on the same network. It seems that the ldap_abandon thrown this
assert because it was a situation like a can't happen. I don't have much
information on the action performed on the firewall which led to this sigabort.
Please find the logs I have :
/lib/sparcv9/libc.so.1:_lwp_kill+0x8 [ Signal 6 (SIGABRT) ]
I am in the process of a reproduction of this signal 6 but I would like to share
the following idea.
Do you think there is a possibility to enhance the openldap library to avoid
this assert? Is it possible that instead of having an assert, we have a
exception or a status code which tell us something went wrong of obviously that
we can handle in our source code.
An assert means there is a bug, either in your code or ours. Since this part
of the library has been around for several years with no issues, that
generally means it's a bug in your code. The way to handle this is to fix your
Trapping or ignoring the conditions that are asserted is just a bad idea.
My best regards
TIBCO Support team
-- Howard Chu
CTO, Symas Corp. http://www.symas.com
Director, Highland Sun http://highlandsun.com/hyc/
Chief Architect, OpenLDAP http://www.openldap.org/project/