Re: (ITS#8997) openldap-nssov/back ldap segfault

[matt@pallissard.net]

--hs6rsxv3pygoehyq
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

On 2019-03-20T22:01:40, Howard Chu wrote:
> matt@pallissard.net wrote:
>
> > 2. Turning the log level to 0 /seems/ to make the issue go away. I'll report
> > back once I can confirm that.
>
> That would imply the SEGV is specifically due to a NULL pointer being passed in a Debug message.
> If that's true, you should be able to reproduce this using whatever accounts aren't fully populated
> with POSIX attributes.
>
> >   A note on this; We do have a good handful of 'service accounts' that don't
> > have all of the posix attributes in active directory.  As such those entries do
> > spam the logs a bit.

I have a backtrace I can submit.  What's the proper way of doing so?  As there is ldap info in it I'd rather not have it publicly accessable.

Matt Pallissard

--hs6rsxv3pygoehyq
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iHUEABYIAB0WIQTvIUMPApUGn6YFkXl1uof+t048SQUCXJQMhgAKCRB1uof+t048
SbqCAQDSEgiivcwR6cztHGogp+hn5+2pikvZ/djpH5XVkRBD7gD9EhqWRSW8QOeY
yPjj8smWGuoO+nbF8VIoGm3Mtw4PCA8=
=cG48
-----END PGP SIGNATURE-----

--hs6rsxv3pygoehyq--