20 Jun
2014
20 Jun
'14
8:39 a.m.
On 20/06/14 13:29, Arran Cudbard-Bell wrote:
Confirmed lack of explodyness.
I also fixed some other explicit frees of VPs which were associated with the EAP specific opaque data.
I'm still able to trigger a crash with #8bd9429 and my local config :o( I think it's harder i.e. takes longer, but similar sort of things: talloc: access after free error - first free may be at src/lib/valuepair.c:171 Bad talloc magic value - access after free talloc abort: Bad talloc magic value - access after free I have a core file, I'll take a look.