[splint-discuss] DIR *dire storage created but not released??

[Michael Wojcik]

> From: splint-discuss-bounces at cs.virginia.edu [mailto:splint-discuss-
> bounces at cs.virginia.edu] On Behalf Of Greg White
> Sent: Friday, 07 November, 2008 13:57
> 
> If I do an open and close on dire and get a warning about fresh
storage
> being created when I open and not being released when I close there is
> a bug somewhere.

Except that you did not have Splint configured correctly.

If the problem still occurs when you run Splint with +posixlib (and
eliminate any other warnings), then yes, that would be a bug. And
certainly Splint has bugs - as much of the traffic on this list will
attest.

My point was simply that you were jumping the gun a bit calling it a
bug, since Splint was telling you that you weren't running it correctly.
And that in particular you hadn't told Splint to use the POSIX library
support, which might have something to do with a false positive from a
POSIX function.

On the other hand, since Splint recognized that opendir allocated memory
even without +posixlib, I would have expected (perhaps unfairly) it to
recognize that closedir would free that memory. So I wouldn't be
surprised if this is a bug; I just don't want to conclude that it is
without due diligence.

-- 
Michael Wojcik
Principal Software Systems Developer, Micro Focus