From: Mark Wielaard <mark@klomp.org>
To: Robert Yang <liezhi.yang@windriver.com>
Cc: elfutils-devel@sourceware.org
Subject: Re: [PATCH V2] libelf/elf_end.c: check data_list.data.d.d_buf before free it
Date: Thu, 30 Aug 2018 19:57:00 -0000 [thread overview]
Message-ID: <20180830195709.GD28085@wildebeest.org> (raw)
In-Reply-To: <1535532800-35485-2-git-send-email-liezhi.yang@windriver.com>
On Wed, Aug 29, 2018 at 04:53:20PM +0800, Robert Yang wrote:
> The one which actually saves the data is data_list.data.d.d_buf, so check it
> before free rawdata_base.
>
> This can fix a segmentation fault when prelink libqb_1.0.3:
> prelink: /usr/lib/libqb.so.0.18.2: Symbol section index outside of section numbers
>
> The segmentation fault happens when prelink call elf_end().
Are you sure this isn't a bug in prelink like we discussed last time?
If it isn't, can you give a short example how this issue happens?
Thanks,
Mark
next prev parent reply other threads:[~2018-08-30 19:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-29 8:42 [PATCH V1] " Robert Yang
2018-08-29 8:42 ` [PATCH V2] " Robert Yang
2018-08-30 19:57 ` Mark Wielaard [this message]
2018-08-31 2:14 ` Robert Yang
2018-08-31 9:35 ` Mark Wielaard
2018-09-03 1:32 ` Robert Yang
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=20180830195709.GD28085@wildebeest.org \
--to=mark@klomp.org \
--cc=elfutils-devel@sourceware.org \
--cc=liezhi.yang@windriver.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).