On Wed, Feb 25, 2015 at 9:53 AM, Alan Conway <acon...@redhat.com> wrote:
> On Wed, 2015-02-25 at 09:04 -0500, Michael Goulish wrote: > > Good point! I'm afraid it will take me the rest of my life > > to reproduce under valgrind .. but ... I'll see what I can do.... > > Try this in your environment: > export MALLOC_PERTURB_=66 > That will cause malloc to immediately fill freed memory with 0x42 bytes > so it is obvious when you gdb the core dump if someone is using freed > memory. > > It's not as informative as valgrind but has no peformance impact that I > can detect, and it often helps to crash faster and closer to the real > problem. Freed memory can hold valid-seeming values for a while so your > code may not notice immediately, whereas 4242424242 is rarely valid for > anything. > > > In the meantime -- I'm not sure what to do with a Jira if the > > provenance is in doubt... > > Maybe just put a note on it till we know more. > +1 FWIW, given that it looks like we are gonna wait for Andrew's SASL changes to land, and Gordon is away till the end of the week and still working on some documentation that would be nice to get into the release, I suspect you have at least a few days to investigate the issue before we get a release candidate for 0.9. --Rafael