From: 陈金佳 <chenjinjia_cn@163.com>
To: "libc-help@sourceware.org" <libc-help@sourceware.org>
Subject: need help about __stack_chk_guard
Date: Mon, 25 Sep 2023 08:53:53 +0800 (GMT+08:00) [thread overview]
Message-ID: <436d1f6d.210bb.18ac9d41133.Coremail.chenjinjia_cn@163.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 913 bytes --]
hello, i am a developer from china and i have encountered a tricky problem in the current development process.
I need to compile a dynamic library, but i don't want to use symbols with "@GLIBC in the dynamic library, because it needs to be used in different glibc runtime environments. Therefore, during the compilation and linking process, I used the -Wl,--wrap compilation option to change the glibc symbols used to __wrap_xxxx. However, this method only works for functions. Because i must use "-fstack-protector-strong",the compiled dynamic library will add "__stack_chk_guard" symbol, which is an OBJECT and cannot be replaced. I hope to get some help from you.
1. Is there a way to replace "__stack_chk_guard" or remove "@GLIBC_2.4" from "__stack_chk_guard@GLIBC_2.4"?
2.If there is no way to replace it, is "__stack_chk_guard" only avaliable in the GLIBC2.4 version within visible time?
thank you!
next reply other threads:[~2023-09-25 0:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-25 0:53 陈金佳 [this message]
2023-09-27 11:59 ` Adhemerval Zanella Netto
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=436d1f6d.210bb.18ac9d41133.Coremail.chenjinjia_cn@163.com \
--to=chenjinjia_cn@163.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).