memory leak in some Kerberos APIs?
Kent_Wu@trendmicro.com
Kent_Wu at trendmicro.com
Thu Jun 12 20:52:09 EDT 2003
Tom:
I just gave it a shot and Bingo, you guys did fix the memory leak in those preauth code. However it introduced some other new leaks in GSS-API side as well. The last one from get_profile_etype_list() is actually the same as last time, it didn't get fixed. The first two are new leaks. Here is the detailed report:
Actual leaks report (actual leaks: 3 total size: 48 bytes)
Total Num of Leaked Allocation call stack
Size Blocks Block
Address
====== ====== ========== =======================================
24 1 0x2e878 make_gss_checksum<-make_ap_req_v1<-
krb5_gss_init_sec_context<-gss_init_sec_context<-main
16 1 0x2c5e0 get_addr<-getaddrinfo<-krb5_sname_to_principal<-
krb5_gss_import_name<-gss_import_name<-main
8 1 0x2d170 get_profile_etype_list<-krb5_get_tgs_ktypes<-
krb5_gss_init_sec_context<-gss_init_sec_context<-main
Let me know if you guys fix it and put on a new Beta candidate.
Thx.
Kent
-----Original Message-----
From: Kent Wu (RD-US)
Sent: Thursday, June 12, 2003 4:42 PM
To: tlyu at mit.edu
Cc: krbdev at mit.edu
Subject: RE: memory leak in some Kerberos APIs?
Hi, Tom:
I'll give it a try and let us know when it got released.
Thx.
Kent
-----Original Message-----
From: Tom Yu [mailto:tlyu at mit.edu]
Sent: Thursday, June 12, 2003 3:51 PM
To: Kent Wu (RD-US)
Cc: krbdev at mit.edu
Subject: Re: memory leak in some Kerberos APIs?
>>>>> "Kent_Wu" == <Kent_Wu at trendmicro.com> writes:
Kent_Wu> Actual leaks report (actual leaks: 4 total size: 57 bytes)
Kent_Wu> Total Num of Leaked Allocation call stack
Kent_Wu> Size Blocks Block
Kent_Wu> Address
Kent_Wu> ====== ====== ========== =======================================
Kent_Wu> 25 1 0x2bbd8 asn1buf_remove_octetstring<-
Kent_Wu> asn1_decode_octetstring<-asn1_decode_etype_info_entry<-asn1_decode_etype_info
Kent_Wu> <-decode_krb5_etype_info<-krb5_do_preauth<-krb5_get_init_creds<-
Kent_Wu> krb5_get_init_creds_password
Kent_Wu> 16 1 0x2ab88 calloc<-asn1_decode_etype_info<-
Kent_Wu> decode_krb5_etype_info<-krb5_do_preauth<-krb5_get_init_creds<-
Kent_Wu> krb5_get_init_creds_password<-main
Kent_Wu> 8 1 0x2b2b8 get_profile_etype_list<-krb5_get_tgs_ktypes<-
Kent_Wu> krb5_gss_init_sec_context<-gss_init_sec_context<-main
Kent_Wu> 8 1 0x36248 asn1_decode_etype_info<-decode_krb5_etype_info<-
Kent_Wu> krb5_do_preauth<-krb5_get_init_creds<-krb5_get_init_creds_password<-main
Have you tried compiling with one of the beta releases of krb5-1.3? I
seem to recall that we have fixed some preauth-related memorly leaks.
---Tom
_______________________________________________
krbdev mailing list krbdev at mit.edu
https://mailman.mit.edu/mailman/listinfo/krbdev
More information about the krbdev
mailing list