From: "Guillermo E. Martinez" <guillermo.e.martinez@oracle.com>
To: Mark Wielaard <mark@klomp.org>
Cc: elfutils-devel@sourceware.org,
"Jose E. Marchesi" <jemarch@gnu.org>,
nickc@redhat.com
Subject: Re: [PATCHv2] strip: keep .ctf section in stripped file
Date: Wed, 22 Feb 2023 11:12:07 -0600 [thread overview]
Message-ID: <20230222171207.xfklpsdy2655bc4c@kamehouse> (raw)
In-Reply-To: <d87d10dca323e8e3823212ecbc8b3c3a87afbd1c.camel@klomp.org>
On Wed, Feb 22, 2023 at 05:42:45PM +0100, Mark Wielaard wrote:
> Hi,
>
Hi Mark,
> On Tue, 2022-12-20 at 22:35 +0100, Mark Wielaard wrote:
> > On Wed, Jun 01, 2022 at 10:55:27AM -0500, Guillermo E. Martinez via Elfutils-devel wrote:
> > > This is the second version patch to avoid remove the CTF section in
> > > stripped files. Changes from v1:
> > >
> > > - Add description in tests/run-strip-remove-keep-ctf.sh
> > > mentioning how to regenerate test input file (testfile-ctf)
> > >
> > > Please let me know your thoughts.
> > >
> > > [...]
> > >
> > > CTF debug format was designed to be present in stripped files, so
> > > this section should not be removed, so a new --remove-ctf option
> > > is added to indicate explicitly that .ctf section will be stripped
> > > out from binary file.
> >
> > Sorry, I see I never reviewed this v2 variant. I know we tried to
> > coordinate with binutils so eu-strip and binutils strip would do the
> > same thing. And that Jose had an idea for a new section flag to
> > automatically detect what section should/shouldn't be stripped (into a
> > separate .debug file). What was the conclusion of that?
>
> Any update on this?
> How should .ctf sections be dealt with by strip like tools?
>
Sorry for late reply,
The conclusion was basically not use section flags to identify which
section should be stripped out or not, so, it requires other mechanisms
for explicitly specifying which sections should be removed, as eu-strip
does using arguments.
https://sourceware.org/bugzilla/show_bug.cgi?id=29737
Worth it mention here, that my last test shows that .ctf section is not
stripped by ue-strip because it doesn't have a "debug" section name.
Thanks,
guillermo
next prev parent reply other threads:[~2023-02-22 17:12 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-31 2:26 [PATCH] " Guillermo E. Martinez
2022-05-31 7:06 ` Mark Wielaard
2022-05-31 10:26 ` Jose E. Marchesi
2022-05-31 12:50 ` Jose E. Marchesi
2022-06-01 4:34 ` Guillermo E. Martinez
2022-06-01 15:55 ` [PATCHv2] " Guillermo E. Martinez
2022-12-20 21:35 ` Mark Wielaard
2023-02-22 16:42 ` Mark Wielaard
2023-02-22 16:59 ` Jose E. Marchesi
2023-02-22 17:12 ` Guillermo E. Martinez [this message]
2023-02-22 23:04 ` Mark Wielaard
2023-02-23 18:34 ` Guillermo E. Martinez
2023-02-23 18:42 ` [PATCH v3] " Guillermo E. Martinez
2023-02-24 11:51 ` Mark Wielaard
2023-02-24 16:48 ` Guillermo E. Martinez
2023-02-28 12:24 ` Mark Wielaard
2023-02-28 12:45 ` Nick Clifton
2023-02-28 12:59 ` Nick Clifton
2023-02-28 14:27 ` Mark Wielaard
2023-03-03 2:40 ` Guillermo E. Martinez
2023-03-03 12:15 ` Mark Wielaard
2023-03-03 12:24 ` Nick Clifton
2023-03-04 14:00 ` Guillermo E. Martinez
2023-03-07 14:50 ` Mark Wielaard
2023-03-07 20:47 ` Guillermo E. Martinez
2023-03-08 17:45 ` Nix
2023-03-09 23:08 ` 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=20230222171207.xfklpsdy2655bc4c@kamehouse \
--to=guillermo.e.martinez@oracle.com \
--cc=elfutils-devel@sourceware.org \
--cc=jemarch@gnu.org \
--cc=mark@klomp.org \
--cc=nickc@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).