Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andrew Burgess <andrew.burgess@embecosm.com>
To: Hannes Domani <ssbssa@yahoo.de>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 1/3] pe_bfd_read_buildid memory leak
Date: Wed, 25 Dec 2019 13:47:00 -0000	[thread overview]
Message-ID: <20191225134708.GI3865@embecosm.com> (raw)
In-Reply-To: <20191224122452.1668-1-ssbssa@yahoo.de>

* Hannes Domani via gdb-patches <gdb-patches@sourceware.org> [2019-12-24 13:24:50 +0100]:

> bfd/ChangeLog:
> 
> 2019-12-24  Hannes Domani  <ssbssa@yahoo.de>
> 
> 	* peicode.h (pe_bfd_read_buildid): Free data.
> ---
>  bfd/peicode.h | 2 ++
>  1 file changed, 2 insertions(+)

Patches for binutils-gdb/bfd/* should be posted to the binutils list
(binutils@sourceware.org) for review.

Thanks,
Andrew


> 
> diff --git a/bfd/peicode.h b/bfd/peicode.h
> index e9d205a01a..00ccfa0a44 100644
> --- a/bfd/peicode.h
> +++ b/bfd/peicode.h
> @@ -1396,6 +1396,8 @@ pe_bfd_read_buildid (bfd *abfd)
>  	  break;
>  	}
>      }
> +
> +  free (data);
>  }
>  
>  static const bfd_target *
> -- 
> 2.24.1
> 


  parent reply	other threads:[~2019-12-25 13:47 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20191224122452.1668-1-ssbssa.ref@yahoo.de>
2019-12-24 12:25 ` Hannes Domani via gdb-patches
2019-12-24 12:25   ` [PATCH 3/3] windows_clear_solib " Hannes Domani via gdb-patches
2020-01-03 16:44     ` Tom Tromey
2019-12-24 12:25   ` [PATCH 2/3] solib_target_free_so " Hannes Domani via gdb-patches
2019-12-26 22:55     ` Christian Biesinger via gdb-patches
2020-01-03 16:41       ` Tom Tromey
2020-01-03 16:47         ` Hannes Domani via gdb-patches
2019-12-25 13:47   ` Andrew Burgess [this message]
2019-12-25 14:14     ` [PATCH 1/3] pe_bfd_read_buildid " Hannes Domani via gdb-patches
2019-12-27 16:46       ` Andrew Burgess

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=20191225134708.GI3865@embecosm.com \
    --to=andrew.burgess@embecosm.com \
    --cc=gdb-patches@sourceware.org \
    --cc=ssbssa@yahoo.de \
    /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