Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
result of latest memory leak run
- X-seq: zsh-workers 18543
- From: Felix Rosencrantz <f_rosencrantz@xxxxxxxxx>
- To: zw <zsh-workers@xxxxxxxxxx>
- Subject: result of latest memory leak run
- Date: Fri, 16 May 2003 20:53:24 -0700 (PDT)
- Mailing-list: contact zsh-workers-help@xxxxxxxxxx; run by ezmlm
I ran the latest cvs version of zsh with valgrind in my environment as my main
shell for a few days. I was only able to find one memory leak, I believe
based on the recent fix for (l=() ; vared l):
==21338== 520 bytes in 3 blocks are definitely lost in loss record 9 of 14
==21338== at 0x401667E0: malloc (vg_clientfuncs.c:103)
==21338== by 0x8086AF5: zalloc (mem.c:490)
==21338== by 0x81008E9: zleread (zle_main.c:790)
==21338== by 0x8101D07: bin_vared (zle_main.c:1149)
==21338== by 0x804B2F5: execbuiltin (builtin.c:440)
==21338== by 0x806193A: execcmd (exec.c:2345)
==21338== by 0x805E24E: execpline2 (exec.c:1228)
==21338== by 0x805D776: execpline (exec.c:1018)
I suspect folks could find other leaks or memory errors if they valgrind zsh in
their environments.
-FR.
__________________________________
Do you Yahoo!?
The New Yahoo! Search - Faster. Easier. Bingo.
http://search.yahoo.com
Messages sorted by:
Reverse Date,
Date,
Thread,
Author