kdestroy coredump (fcc_close)

[Leif Johansson <leifj@matematik.su.se>]

Hi all,

fcc_close or some routine close to it does something nasty
with memory causing a __libc_free segfault. Probably some
memory gets freed twice or not allocated properly or something.
This did not happen in 0.0t so it must be due to some recent
change in 0.0u. I enclose the usual gdb sample session showing
exactly where the error occurs. However as you see there does
not seem to be any reason for crashing on this free... Strange!

Breakpoint 1, fcc_close (context=0x8049bd0, id=0x8049ca0) at fcache.c:159
159         free (FILENAME(id));
(gdb) p (((krb5_fcache*)(id)->data.data)->filename)
$7 = 0x804a350 "/tmp/krb5cc_0"

......

(gdb) p *((krb5_fcache*)(id)->data.data)
$9 = {filename = 0x804a350 "/tmp/krb5cc_0", version = 0}
(gdb) s
__libc_free (mem=0x804a350) at malloc.c:2837

This is all on an intel/linux. 

	Cheers Leif

PS cross auth works like a charm! DS