-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 01/07/2011 01:02 PM, Howard Chu wrote:
Howard Chu wrote:
Ondrej Kuznik wrote:
On 01/06/2011 11:17 PM, Quanah Gibson-Mount wrote:
There have been substantial updates to RE24. Please test!
On a different host, RHEL5, x86_64, db 4.7.25 every test ends with a slapd segfault that gets ignored:
Where should I look for further info?
Enable core dumps and examine the core files with gdb.
Yeah, I did that in the meantime, seeing strange backtraces in gdb. I found out later that the fault was in my environment, as I accidentaly let slapd use different libldap than the one it was compiled with. Running with libldap from this testing call made all tests pass OK.
Every time I compile slapd with "--enable-modules" but without "--enable-dynamic", I get symbol resolution errors about libldap functions on every machine aborting the slapd process. Is it expected with this ./configure parameter combination? If so, shouldn't "--enable-modules" imply "--enable-dynamic"?
It's a known issue, but it only shows up with some versions of libtool (and not others).
I have asked this question several times already on openldap-technical/#openldap, but have never received any response.
The FAQ-o-Matic has stock answers for core dump issues, so questions of this nature rarely merit a direct response.
This was not a segfault/core dump issue, that I more or less know what to do with(*), but symbol resolution issue and I believe I have pointed that out then. Also, I did search the FAQ, ITS and mailing lists and concluded that it was not known. However, as you have told me now that this issue is known, it does not matter anymore, so thanks for the info.
(*) well mostly, I've never really investigated a dump where the stack seemed corrupted
BTW: the search at http://www.openldap.org/lists/$LIST/ can't seem to find anything for any query.
PS: This is the -devel list. You're expected to know what's in the FAQ already.
This e-mail and any attachment is for authorised use by the intended recipient(s) only. It may contain proprietary material, confidential information and/or be subject to legal privilege. It should not be copied, disclosed to, retained or used by, any other party. If you are not an intended recipient then please promptly delete this e-mail and any attachment and all copies and inform the sender. Thank you.