From: Antti Tapaninen <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] Subject: Re: MUSCLE PAM module (a bug?)
On Thu, 21 Mar 2002, Jes�s Pa�l wrote: > I have just written a PAM module (with PC/SC lite support) and a PAM > application, both very simple. And I have found that I SHOULD compile > the PAM application with the -lpthread and -lpcsclite flags, even if the > program has no line related with PC/SC lite. > > If I don't use (or forget to use) those flags, that is what happens: > just after exit() from the program, it receives a SIGSEGV signal so it > finishes abnormally its execution. This does not happen if pam_end() is > not called. If this a bug or a feature? :) Hi, I'd guess it's a bug in glibc/pthread code. What glibc version are you using? I found exactly the same problem about 6 months ago and also noticed that -lpthread linking resolves the problem. HUT/CC is currently using an old version of debian (stable with glibc 2.1.3) and the problem doesn't appear with any recent versions of glibc (=2.2.5). HTH, -Antti *************************************************************** Unix Smart Card Developers - M.U.S.C.L.E. (Movement for the Use of Smart Cards in a Linux Environment) http://www.linuxnet.com/ To unsubscribe send an email to [EMAIL PROTECTED] with unsubscribe sclinux ***************************************************************
