From: Peng Yu <pengyu.ut@gmail.com>
To: libc-help <libc-help@sourceware.org>
Subject: Is there a way to distinguish binary files compiled with -D_FORTIFY_SOURCE=1 and -D_FORTIFY_SOURCE=2?
Date: Thu, 8 Apr 2021 19:12:39 -0500 [thread overview]
Message-ID: <CABrM6w=wj42N_1OXTN0N7RnP889+sLKFwZA7ARRkcbTbM8f6Vw@mail.gmail.com> (raw)
https://gcc.gnu.org/legacy-ml/gcc-patches/2004-09/msg02055.html
When I compile a .c file with -D_FORTIFY_SOURCE=1 and
-D_FORTIFY_SOURCE=2, the binary files both contain symbols like
..._chk@...
So I can not tell whether _FORTIFY_SOURCE is 1 or 2 just by whether
symbols have ..._chk@....
Is there a way to tell the difference only from the binary file?
--
Regards,
Peng
next reply other threads:[~2021-04-09 0:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-09 0:12 Peng Yu [this message]
2021-04-09 17:17 ` Carlos O'Donell
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='CABrM6w=wj42N_1OXTN0N7RnP889+sLKFwZA7ARRkcbTbM8f6Vw@mail.gmail.com' \
--to=pengyu.ut@gmail.com \
--cc=libc-help@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).