From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 24075 invoked from network); 31 Jul 2002 02:24:05 -0000 Received: from sunsite.dk (130.225.247.90) by ns1.primenet.com.au with SMTP; 31 Jul 2002 02:24:05 -0000 Received: (qmail 17029 invoked by alias); 31 Jul 2002 02:23:51 -0000 Mailing-List: contact zsh-workers-help@sunsite.dk; run by ezmlm Precedence: bulk X-No-Archive: yes X-Seq: 17493 Received: (qmail 17018 invoked from network); 31 Jul 2002 02:23:50 -0000 Message-ID: <20020731022348.33364.qmail@web10410.mail.yahoo.com> Date: Tue, 30 Jul 2002 19:23:48 -0700 (PDT) From: Felix Rosencrantz Subject: Memory leak in hist.c:histsubchar To: zsh-workers@sunsite.auc.dk MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii I've been running with valgrind, and found this memory leak in histsubchar. Though with my normal usage, this along with a termcap leak were the only leaks I've seen. -FR. ==20401== 92 bytes in 4 blocks are definitely lost in loss record 4 of 17 ==20401== at 0x400467C4: malloc (vg_clientfuncs.c:100) ==20401== by 0x808C602: zalloc (mem.c:490) ==20401== by 0x80ABCA5: ztrdup (string.c:52) ==20401== by 0x8074F72: histsubchar (hist.c:402) __________________________________________________ Do You Yahoo!? Yahoo! Autos - Get free new car price quotes http://autos.yahoo.com