public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Indu Bhagat <indu.bhagat@oracle.com>
To: binutils@sourceware.org
Cc: Indu Bhagat <indu.bhagat@oracle.com>
Subject: [PATCH 0/2] libsframe: fix some memory leaks
Date: Thu, 22 Dec 2022 14:54:55 -0800	[thread overview]
Message-ID: <20221222225457.1095930-1-indu.bhagat@oracle.com> (raw)

Hello,

This patch set fixes some memory leaks in the libsframe and it's testsuite.

Testing notes:
- Reg tested natively on aarch64 and x86_64

Thanks,
Indu Bhagat (2):
  libsframe: fix a memory leak in sframe_decode
  libsframe: testsuite: fix memory leaks in testcases

 libsframe/sframe-impl.h                           | 15 +++++++++++----
 libsframe/sframe.c                                |  9 +++++++++
 .../testsuite/libsframe.decode/be-flipping.c      |  3 +++
 libsframe/testsuite/libsframe.decode/frecnt-1.c   |  3 +++
 libsframe/testsuite/libsframe.decode/frecnt-2.c   |  3 +++
 5 files changed, 29 insertions(+), 4 deletions(-)

-- 
2.37.2


             reply	other threads:[~2022-12-22 22:55 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-22 22:54 Indu Bhagat [this message]
2022-12-22 22:54 ` [PATCH 1/2] libsframe: fix a memory leak in sframe_decode Indu Bhagat
2022-12-22 22:54 ` [PATCH 2/2] libsframe: testsuite: fix memory leaks in testcases Indu Bhagat
2022-12-23  9:55 ` [PATCH 0/2] libsframe: fix some memory leaks Nick Clifton
2022-12-23 15:35   ` Indu Bhagat
2022-12-23 15:39     ` Nick Clifton
2022-12-23 14:22 ` libsframe builder (Was: [PATCH 0/2] libsframe: fix some memory leaks) Mark Wielaard
2022-12-23 14:41   ` Frank Ch. Eigler
2022-12-23 16:06     ` Mark Wielaard
2022-12-23 15:24   ` Indu Bhagat
2022-12-23 16:13     ` Mark Wielaard

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=20221222225457.1095930-1-indu.bhagat@oracle.com \
    --to=indu.bhagat@oracle.com \
    --cc=binutils@sourceware.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).