From: "John T. Guthrie" <guthrie@counterexample.org>
To: zsh-workers@sunsite.dk
Subject: Possible ztrdup memory leaks?
Date: Thu, 20 Feb 2003 03:31:22 -0500 [thread overview]
Message-ID: <200302200831.h1K8VMQ19431@gauss.counterexample.org> (raw)
While going through the code in exec.c, I found the following at line 2876:
nam = ztrdup(nam);
Correct me if I'm wrong, but would this cause a memory leak? I found two other
places in the code where you have something of the form foo=ztrdup(foo): at
line 3408 of exec.c and line 330 of init.c. Since ztrdup() uses zalloc(), I
wasn't certain if something special needed to be done to fix these leaks.
(The first and third of these potential leaks look intuitively easy to fix, but
I'm not certain if the second one is really a leak or not.)
John Guthrie
guthrie@counterexample.org
next reply other threads:[~2003-02-20 8:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-20 8:31 John T. Guthrie [this message]
2003-02-20 10:45 ` Peter Stephenson
2003-02-20 12:57 ` John T. Guthrie
2003-02-21 10:18 ` 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=200302200831.h1K8VMQ19431@gauss.counterexample.org \
--to=guthrie@counterexample.org \
--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).