RE: memory leak problems, I might be doing something wrong

[Thomas Dickey]

On Wed, 13 Dec 2006, chinlu chinawa wrote:

> Anyway, what I reckon one should do in this sort of
> situations is to add suppresion rules to valgrind so
> that unfreed memory won't disturb, which I haven't
> achieved either so far.

That's another solution (I've noticed that Debian's package for
valgrind does contain suppression rules).  But it's specific to
valgrind.

> At last patch-level, within include/MKhashsize.sh,
> line 38, one can see something like this:
>
> TABSIZE=`grep -v '^[ #]' $CAPS | grep -v "^$" | grep
> -v "^capalias"| grep -v "\
> ^infoalias" | wc -l'

yes - bash was treating the '#' as a comment marker.

> and I always have to change it to something like this:
>
> TABSIZE=$(grep -v '^[ #]' $CAPS | grep -v "^$" | grep
> -v "^capalias"| grep -v "\
> ^infoalias" | wc -l)
>
> though as I'm not an expert I'm not sending a patch or
> even say you might have to correct it, is just that I
> always find problems in that stage of the process,
> which IIRC is for building up curses.h.
>
> My system's info is:
>
> GNU bash, version 3.2.0(10)-release

That's a defect reported in bash 3.2 within a few days of its release 
(there were others but did not affect ncurses).  I think most of those 
have been addressed (and updating bash is supposed to fix it).

--
Thomas E. Dickey
http://invisible-island.net
ftp://invisible-island.net