Well, there is one UMB in fe-connect.c that annoys the hell out of me. It
has to do with variable pacBuf .... I spend some time tracking it
down...so far I failed :(....Apparently Purify on SunOS gives slightly
more info concerning UMR's so I'll work from there...
I ran the the backend under purify today...Damn Irix...the NIS stuff
almost makes Purify cry....But I did find a few leaks in the
postgres buffer manager...
=+=------------------------/\---------------------------------=+=
Igor Natanzon |**| E-mail: igor@sba.miami.edu
=+=------------------------\/---------------------------------=+=
On Tue, 3 Jun 1997, Tymm Twillman wrote:
> > > If I remember correctly, not all of there problems from Purifying the
> > > backend were memory leaks....there were array bounds errors ( should be
> > > easy to track down) and uninitialized memory being read...stuff like
> > > that...should be interesting...
>
> I checked the UMR's; all of them are generated between 2 lines of code:
>
> fe-connect.c:
>
> pe = getprotobyname ("TCP");
>
> fe-auth.c:
>
> struct passwd *pw = getpwuid(geteuid());
>
> They are not postgeSQL code errors (yay :) )... They're all from NIS
> passing things around.
>
> BTW, Igor: wonderful job on the psql patches-- my tests confirm the no
> leaked bytes on regression tests.
>
> -Tymm
>
------------------------------
