Re: [Bug-readline] Readline memory leak

[Chet Ramey]

> I am using libreadline 6.1 and I've found that valgrind reports still
> reachable memory. It's a very simple piece of code:

Reachable memory means it's not leaked.  The application or library still
holds handles to it.

> > ==9958== LEAK SUMMARY:
> > ==9958==    definitely lost: 0 bytes in 0 blocks
> > ==9958==    indirectly lost: 0 bytes in 0 blocks
> > ==9958==      possibly lost: 0 bytes in 0 blocks
> > ==9958==    still reachable: 42,911 bytes in 154 blocks
> > ==9958==         suppressed: 0 bytes in 0 blocks
> > ==9958== Rerun with --leak-check=full to see details of leaked memory
> > ==9958==
> > ==9958== For counts of detected and suppressed errors, rerun with: -v
> > ==9958== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 13 from 8)
> >
> >
> I just wanted to know if this is supposed to be this way or if it's some
> kind of bug.

Since valgrind reports no leaks, and there aren't any details concerning
the still-reachable allocations, I'm going to assume that everything is OK.

Chet

-- 
``The lyf so short, the craft so long to lerne.'' - Chaucer
                 ``Ars longa, vita brevis'' - Hippocrates
Chet Ramey, ITS, CWRU    address@hidden    http://cnswww.cns.cwru.edu/~chet/