Date: Tue, 18 Nov 2014 11:08:53 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-bugs@FreeBSD.org Subject: [Bug 195128] Memory leaks in lib/libpam/modules due to memory handling with login_getcapstr, et al Message-ID: <bug-195128-8-T6RMc5DXbg@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-195128-8@https.bugs.freebsd.org/bugzilla/> References: <bug-195128-8@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D195128 --- Comment #2 from Dag-Erling Sm=C3=83=C2=B8rgrav <des@FreeBSD.org> --- Wait. Actually, the login_cap(3) man page says: Once a program no longer wishes to use a login_cap_t object, login_close() may be called to free all resources used by the login class. The login_close() function may be passed a NULL pointer with no harmful side-effects. so this should not be a problem. Or did I miss something? --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-195128-8-T6RMc5DXbg>