Re: [Nano-devel] splint finds memory-leaks in nano.c

[Steven Kneizys]

I am using a hybrid (half mine, half zmalloc) analyzer.  It isn't the
best tool out there, especially my half! ;-)  I posted the basics of it
around Feb 17th.

Steve...

--- Rocco Corsi <address@hidden> wrote:
> Steven Kneizys wrote:
> 
> > I just did a spell check with replace, 'fixed' them and ened up
> with a
> > nearly identical diff file afterwards with the exception of an
> extra
> > free needed.
> > 
> > In files.c, there is a possible bug in check_writable_directory,
> > comment says it is full_path but path is used instead:
> > 
> >     /* otherwise, stat() the full path to see if it's writable by
> the
> >        user; set writable to 1 if it is, or 0 if it isn't */
> >     stat(path, &fileinfo);
> > 
> > There was unfreed memory from checking the writable directory too.
> > 
> > I am still getting the leaks from paths in the do_browser calls :) 
> I
> > will look at them sometime.
> > 
> 
> 
> 
> Did you find these manually or are you using a code analyser?
> 
> Rocco
> 
> 
> 
> 
> 
> _______________________________________________
> Nano-devel mailing list
> address@hidden
> http://mail.gnu.org/mailman/listinfo/nano-devel


__________________________________________________
Do You Yahoo!?
Yahoo! Sports - sign up for Fantasy Baseball
http://sports.yahoo.com