zsh-workers
 help / color / mirror / code / Atom feed
From: Felix Rosencrantz <f_rosencrantz@yahoo.com>
To: zsh-workers@sunsite.dk
Subject: Re: Memory leaks found by valgrind
Date: Fri, 28 Feb 2003 14:07:22 -0800 (PST)	[thread overview]
Message-ID: <20030228220722.16160.qmail@web10406.mail.yahoo.com> (raw)
In-Reply-To: <13316.1045478350@csr.com>

Sorry I haven't had much of a chance to run valgrind with the latest patches,
particularly the one from Peter.  (Thanks Peter, though.)

I noticed that the termcap leak occurs even if I do what I consider to be
a no-op: TERM=$TERM
Doing that repeatedly could leak a bit of memory.  To me, it seems like a
pretty minor issue.

The only new leak I found was the following.   This I believe is related
to replace-string command.  When I tried that widget, I would get more
leaks.  (I haven't tried using other recent features/changes.)
 62 bytes in 62 blocks are definitely lost in loss record 5 of 13
    at 0x40165A60: malloc (vg_clientfuncs.c:100)
    by 0x8086275: zalloc (mem.c:490)
    by 0x810536C: set_prepost (zle_params.c:485)
    by 0x810541E: set_postdisplay (zle_params.c:515)
    by 0x808F7F4: setstrvalue (params.c:1608)
    by 0x8090BAC: assignsparam (params.c:1994)
    by 0x805F0A6: addvars (exec.c:1598)
    by 0x805CDC9: execsimple (exec.c:756)

-FR.


__________________________________________________
Do you Yahoo!?
Yahoo! Tax Center - forms, calculators, tips, more
http://taxes.yahoo.com/


  reply	other threads:[~2003-02-28 22:07 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-08 18:03 Felix Rosencrantz
2003-02-17  9:44 ` Memory leaks found by valgrind (try2) Felix Rosencrantz
2003-02-17 10:39 ` Memory leaks found by valgrind Peter Stephenson
2003-02-28 22:07   ` Felix Rosencrantz [this message]
2003-03-05 13:59     ` Peter Stephenson

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20030228220722.16160.qmail@web10406.mail.yahoo.com \
    --to=f_rosencrantz@yahoo.com \
    --cc=zsh-workers@sunsite.dk \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/zsh/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).