From: Mark Wielaard <mark@klomp.org>
To: "Guillermo E. Martinez" <guillermo.e.martinez@oracle.com>
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: Thu, 23 Feb 2023 00:04:47 +0100 [thread overview]
Message-ID: <20230222230447.GD1713@gnu.wildebeest.org> (raw)
In-Reply-To: <20230222171207.xfklpsdy2655bc4c@kamehouse>
Hi,
On Wed, Feb 22, 2023 at 11:12:07AM -0600, Guillermo E. Martinez wrote:
> 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
OK, thanks.
> 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.
Are you sure that is what happens? It might depend on whether or not
you give eu-strip -g or not.
With -g only debug symbols and .debug sections are removed, but it
keeps any other unused/unallocated symbol/section. Without -g I would
expect eu-strip to remove the .ctf section (unless it is an allocated
section or referenced from an allocated section/symbol table).
Cheers,
Mark
next prev parent reply other threads:[~2023-02-22 23:04 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
2023-02-22 23:04 ` Mark Wielaard [this message]
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=20230222230447.GD1713@gnu.wildebeest.org \
--to=mark@klomp.org \
--cc=elfutils-devel@sourceware.org \
--cc=guillermo.e.martinez@oracle.com \
--cc=jemarch@gnu.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).