unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Dmitry Bogatov <KAction@gnu.org>
To: dsmich@roadrunner.com
Cc: guile-devel@gnu.org
Subject: Re: [PATCH 1/2] Fix memory leak on `realloc' failure
Date: Thu, 10 Apr 2014 20:52:43 +0400	[thread overview]
Message-ID: <20140410165243.GA16599@localhost.kaction.name> (raw)
In-Reply-To: <20140410163648.MIXO2.198633.root@cdptpa-web07>

* dsmich@roadrunner.com <dsmich@roadrunner.com> [2014-04-10 12:36:48-0400]
> > +	      {
> > +		free (nargv);
> >  	        return 0L;
> > +	      }
> >  	    else
> >  	      nargv[nargi++] = narg;
> I don't understand this.  In both cases, free() will be called with an
> argument of 0, which does nothing.

My bad. It does not fix problem, that if realloc fails, it does not free
memory, but we blindly assign, losing pointer to previous memory chunk.

I will make another patch, like this

void* xrealloc(void *old_ptr, size_t new_size)
{
        void *new_ptr = realloc(old_ptr, new_size);
        if (!new_ptr)
                free(old_ptr);
        return new_ptr;
}

Suggestions, maybe more conventional name?

--
Best regards, Dmitry Bogatov <KAction@gnu.org>,
Free Software supporter, esperantisto and netiquette guardian.
	git://kaction.name/rc-files.git
	GPG: 54B7F00D



  reply	other threads:[~2014-04-10 16:52 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-10  5:37 [PATCH 1/2] Fix memory leak on `realloc' failure KAction
2014-04-10  5:37 ` [PATCH 2/2] Reduce scope of variables KAction
2014-04-10 16:36 ` [PATCH 1/2] Fix memory leak on `realloc' failure dsmich
2014-04-10 16:52   ` Dmitry Bogatov [this message]
2014-04-12  6:59     ` Dmitry Bogatov
2014-04-22 20:25       ` Andy Wingo

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

  List information: https://www.gnu.org/software/guile/

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

  git send-email \
    --in-reply-to=20140410165243.GA16599@localhost.kaction.name \
    --to=kaction@gnu.org \
    --cc=dsmich@roadrunner.com \
    --cc=guile-devel@gnu.org \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).