Failing autobuilds with a segfault in winbindd
Volker.Lendecke at SerNet.DE
Wed Oct 18 11:06:47 UTC 2017
On Tue, Oct 17, 2017 at 04:12:33PM +1300, Andrew Bartlett via samba-technical wrote:
> G'Day Volker,
> I've noticed two recent autobuild failures showing a segfault in winbindd.
> They started only this week (I've checked back to the start of July)
> Giving that the failure is in operating on a netlogon pipe and the
> recent changes that I reviewed for you to the winbind code,
> I wondered if you would might be able to look into this to see if you
> can work out what is going wrong?
Stared at the code, but I didn't find any code path where we would
leave cli->binding_handle uninitialized. It seems that in all three
instances "h" is 500000000000401, which sounds like a memory
corruption that might come from anywhere. Is there a way we can run
the flaky check (or a private autobuild) with winbind under valgrind?
SerNet GmbH, Bahnhofsallee 1b, 37081 Göttingen
phone: +49-551-370000-0, fax: +49-551-370000-9
AG Göttingen, HRB 2816, GF: Dr. Johannes Loxen
http://www.sernet.de, mailto:kontakt at sernet.de
More information about the samba-technical