[prev in list] [next in list] [prev in thread] [next in thread] 

List:       openldap-bugs
Subject:    [Issue 10096] SIGSEGV in try_read1msg() while using referrals with AD
From:       openldap-its () openldap ! org
Date:       2023-08-30 22:19:54
Message-ID: bug-10096-2-VsoQIkJEy5 () http ! bugs ! openldap ! org/
[Download RAW message or body]

https://bugs.openldap.org/show_bug.cgi?id=10096

--- Comment #2 from Simon Pichugin <simon.pichugin@gmail.com> ---
(In reply to Ondřej Kuzník from comment #1)
> Hi Simon,
> given you can repro it and seems you're suggesting it's hard to
> reproduce without an AD, can you:
> - try running it under valgrind's memcheck and post any errors reported,
>   tracing memory origins as well (I suspect the request has been freed
>   already)
> - enable libldap's TRACE logging and post the logs here?
> 
> That's assuming you can't wrap something up that we could use to
> reproduce the issue ourselves, that would obviously be preferable.
> 
> Thanks,

Hi Ondřej,
Unfortunately, the source's a customer case, and it's closed now (as the
correct settings are 'ldap_referrals = false' for AD config).
Hence, I wasn't able to extract more information.

I've tried to debug it myself first, but the most suspicious place I found is
this one:
https://git.openldap.org/openldap/openldap/-/blob/master/libraries/libldap/result.c#L866

But I'm not sure how we could end up there when we chase the referral while
it's AD (and somehow a parent is involved?).

Valgrind and debug logging was my next suggestion, but the work with the
customer was successfully finished.

So unless you have more ideas looking at the stack trace, I'm not sure how to
proceed, sorry...

-- 
You are receiving this mail because:
You are on the CC list for the issue.=
[prev in list] [next in list] [prev in thread] [next in thread]