From: "jpalus at fastmail dot com" <sourceware-bugzilla@sourceware.org>
To: elfutils-devel@sourceware.org
Subject: [Bug tools/29498] New: Is it expected that eu-strip strips .note.GNU-stack
Date: Tue, 16 Aug 2022 21:23:27 +0000 [thread overview]
Message-ID: <bug-29498-10460@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=29498
Bug ID: 29498
Summary: Is it expected that eu-strip strips .note.GNU-stack
Product: elfutils
Version: unspecified
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: tools
Assignee: unassigned at sourceware dot org
Reporter: jpalus at fastmail dot com
CC: elfutils-devel at sourceware dot org
Target Milestone: ---
Accidentally we've started to strip crt*.o files produced by glibc and were
surprised by the fact that eu-strip gets rid of .note.GNU-stack section
resulting in incorrect linking.
$ gcc -c test.c -o test.o
$ readelf -S test.o|grep GNU-stack
[ 5] .note.GNU-stack PROGBITS 0000000000000000 00000074
$ eu-strip test.o
$ readelf -S test.o|grep GNU-stack
(empty)
I see following comment in strip.c:
> - special sections named ".comment" and ".note" are kept
https://sourceware.org/git/?p=elfutils.git;a=blob;f=src/strip.c;h=452b12796dd3b7ff3a46d13a2bfb9aa0f5c93ac9;hb=HEAD#l1361
The question is whether observed behavior is expected or rather .note.GNU-stack
should be kept?
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2022-08-16 21:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-16 21:23 jpalus at fastmail dot com [this message]
2022-08-17 7:16 ` [Bug tools/29498] " mliska at suse dot cz
2022-10-27 20:34 ` mark at klomp dot org
2022-10-28 23:06 ` jpalus at fastmail dot com
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=bug-29498-10460@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.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).