From: Jim Blandy <jimb@codesourcery.com>
To: msnyder@sonic.net
Cc: gdb-patches@sourceware.org, bug-readline@gnu.org
Subject: Re: PATCH: readline/histexpand.c, resource leak
Date: Wed, 15 Aug 2007 00:01:00 -0000 [thread overview]
Message-ID: <m3d4xpr7i7.fsf@codesourcery.com> (raw)
In-Reply-To: <10015.12.7.175.2.1185934493.squirrel@webmail.sonic.net> (msnyder@sonic.net's message of "Tue, 31 Jul 2007 19:14:53 -0700 (PDT)")
It seems to me that 'words' is a malloc'ed array of malloc'ed strings,
so 'free (words)' still leaks storage.
msnyder@sonic.net writes:
> 2007-07-31 Michael Snyder <msnyder@access-company.com>
>
> * histexpand.c (history_find_word): Resource leak.
>
> Index: histexpand.c
> ===================================================================
> RCS file: /cvs/src/src/readline/histexpand.c,v
> retrieving revision 1.6
> diff -p -r1.6 histexpand.c
> *** histexpand.c 5 May 2006 18:26:12 -0000 1.6
> --- histexpand.c 1 Aug 2007 02:08:51 -0000
> *************** history_find_word (line, ind)
> *** 1581,1588 ****
> int i, wind;
>
> words = history_tokenize_internal (line, ind, &wind);
> ! if (wind == -1 || words == 0)
> return ((char *)NULL);
> s = words[wind];
> for (i = 0; i < wind; i++)
> free (words[i]);
> --- 1581,1594 ----
> int i, wind;
>
> words = history_tokenize_internal (line, ind, &wind);
> ! if (words == NULL)
> return ((char *)NULL);
> + if (wind == -1)
> + {
> + free (words);
> + return ((char *)NULL);
> + }
> +
> s = words[wind];
> for (i = 0; i < wind; i++)
> free (words[i]);
next prev parent reply other threads:[~2007-08-15 0:01 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-01 2:14 msnyder
2007-08-10 21:32 ` msnyder
2007-08-15 0:01 ` Jim Blandy [this message]
2007-08-15 0:38 ` msnyder
2007-08-15 1:20 ` Daniel Jacobowitz
2007-08-15 1:40 ` msnyder
2007-08-15 21:43 ` Jim Blandy
2007-08-18 20:12 ` [Bug-readline] " Chet Ramey
2007-08-18 20:15 ` msnyder
2007-08-20 17:03 ` Jim Blandy
2007-08-22 2:02 ` Chet Ramey
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=m3d4xpr7i7.fsf@codesourcery.com \
--to=jimb@codesourcery.com \
--cc=bug-readline@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=msnyder@sonic.net \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox