public inbox for elfutils@sourceware.org
 help / color / mirror / Atom feed
From: Mark Wielaard <mark@klomp.org>
To: elfutils-devel@sourceware.org
Subject: Re: [PATCH] libebl: ebl_object_note print 32bit annobin address ranges correctly
Date: Tue, 27 Feb 2024 15:58:31 +0100	[thread overview]
Message-ID: <a75ab29af9d57e3d0a165c4c2c53a710bbd58f84.camel@klomp.org> (raw)
In-Reply-To: <20240221205914.2144167-1-mark@klomp.org>

Hi,

On Wed, 2024-02-21 at 21:59 +0100, Mark Wielaard wrote:
> Annobin address ranges were always printed as if they were 64bit wide
> because addr_size was set to twice the size. This was done because the
> note description size should contain two addresses. Fix this by setting
> the address size to just one address and then check that descsz is
> twice that.
> 
> 	* libebl/eblobjnote.c (ebl_object_note): Set addr_size to one
> 	ELF_T_ADDR. Check descsz equals two times addr_size.

After a quick chat with Aaron on irc I pushed this.

Cheers,

Mark

      reply	other threads:[~2024-02-27 14:58 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-21 20:59 Mark Wielaard
2024-02-27 14:58 ` Mark Wielaard [this message]

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=a75ab29af9d57e3d0a165c4c2c53a710bbd58f84.camel@klomp.org \
    --to=mark@klomp.org \
    --cc=elfutils-devel@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).