From: Tom de Vries <tdevries@suse.de>
To: dwz@sourceware.org, jakub@redhat.com
Subject: Re: [PATCH] Handle unsorted section header table
Date: Tue, 01 Jan 2019 00:00:00 -0000 [thread overview]
Message-ID: <7dd48bbc-bfb4-ba7c-00c0-260f88a9c1d2@suse.de> (raw)
In-Reply-To: <20190312170735.GA21660@delia>
On 12-03-19 18:07, Tom de Vries wrote:
> Hi,
> Handle unsorted section header table in write_dso by:
> - rewriting loop (*) in sh_offset updating code to handle unsorted section
> header table
> (*) Specifically, this one:
> ...
> for (j = dso->ehdr.e_shstrndx + 1; j < dso->ehdr.e_shnum; ++j)
> dso->shdr[j].sh_offset += len;
> ...
>
I realized that this in itself is a potential wrong-code issue,
submitted patch for it here (
https://sourceware.org/ml/dwz/2019-q1/msg00127.html ).
Thanks,
- Tom
next prev parent reply other threads:[~2019-03-15 15:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-01 0:00 Tom de Vries
2019-01-01 0:00 ` Tom de Vries [this message]
2019-01-01 0:00 ` [committed][PATCH] " Tom de Vries
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=7dd48bbc-bfb4-ba7c-00c0-260f88a9c1d2@suse.de \
--to=tdevries@suse.de \
--cc=dwz@sourceware.org \
--cc=jakub@redhat.com \
/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).