Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!rice!uw-beaver!mit-eddie!mintaka!yale!think!samsung!rex!mb
From: mb@rex.cs.tulane.edu (Mark Benard)
Newsgroups: comp.unix.questions
Subject: Re: RPC programming
Message-ID: <2508@rex.cs.tulane.edu>
Date: 14 Mar 90 23:57:50 GMT
References: <8008@cs.utexas.edu> <3744@incas.informatik.uni-kl.de>
Reply-To: mb@rex.UUCP (Mark Benard)
Distribution: comp
Organization: Computer Science Dept., Tulane Univ., New Orleans, LA
Lines: 18

In article <3744@incas.informatik.uni-kl.de> zessel@descartes.informatik.uni-kl.de (Holger Zessel) writes:
>tph@cs.utexas.edu (Pow-Hwee Tan) writes:
>>2.  The XDR serializing/deserializing routines do not explicitly free
>>the memory allocated.  How can I free them myself?
>
>This would interest me too. I write some kind of NFS-Server. Now
>I have the problem that ist prototypes are growing permanently while
>serving NFS-requests. I could not find any reason for this memory leak
>in my code.

Won't xdr_free() do the job?

Mark
-- 
Mark Benard
Department of Computer Science     INTERNET & BITNET: mb@cs.tulane.edu
Tulane University                  USENET:   rex!mb
New Orleans, LA 70118