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

[chinlu chinawa]

Hello Thomas,

>If you configure ncurses (at build time of course) 
>using --disable-leaks,

Well I couldn't manage to handle this via ncurses, it
doesn't free all the memory up as you say.

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.

I also forgot to mention a problem I've been having
this last times for compiling ncurses.

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'

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
(i686-pc-linux-gnu)
Copyright (C) 2005 Free Software Foundation, Inc.

Kind Regards,




                
___________________________________________________________ 
Try the all-new Yahoo! Mail. "The New Version is radically easier to use" – The 
Wall Street Journal 
http://uk.docs.yahoo.com/nowyoucan.html