From: Adhemerval Zanella Netto <adhemerval.zanella@linaro.org>
To: Joel GUITTET <jguittet.opensource@witekio.com>,
"libc-help@sourceware.org" <libc-help@sourceware.org>
Subject: Re: glibc testsuite RELRO error
Date: Wed, 17 Apr 2024 13:01:39 -0300 [thread overview]
Message-ID: <7a1a44fb-a825-4f99-abf5-af73bc2cbe97@linaro.org> (raw)
In-Reply-To: <AM9P192MB1316856671C448E578D257A8D70F2@AM9P192MB1316.EURP192.PROD.OUTLOOK.COM>
It uses to fail with --with-default-link=yes, since on 2.35 the stdio
vtables was places on relro segment explicit by an asm macro
(__libc_IO_vtables) and an processed linker script. We removed it this
limitation on recent version (91fc5b99907655bc04cf23247b5fe0ae0ca6e9eb).
On 17/04/24 10:26, Joel GUITTET wrote:
> Sure, this is glibc 2.35, gcc 11.4 and binutils 2.38.
>
> ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
> *De :* Adhemerval Zanella Netto <adhemerval.zanella@linaro.org>
> *Envoyé :* mercredi 17 avril 2024 14h18
> *À :* Joel GUITTET <jguittet.opensource@witekio.com>; libc-help@sourceware.org <libc-help@sourceware.org>
> *Objet :* Re: glibc testsuite RELRO error
>
> [Vous ne recevez pas souvent de courriers de adhemerval.zanella@linaro.org. Découvrez pourquoi ceci est important à https://aka.ms/LearnAboutSenderIdentification <https://aka.ms/LearnAboutSenderIdentification> ]
>
> On 16/04/24 12:23, Joel GUITTET via Libc-help wrote:
>> Hello,
>>
>> I'm executing the glibc testsuite and I get an error on "glibc-testsuite.elf/tst-relro-libc": "_IO_wstrn_jumps of size 1113704 at 0x54 is not in RELRO range [0x10dc8c, 0x10f000]"
>>
>> It seems first the start and size values are crossed, but by the way, what means this error ?
>>
>> Thanks for any inputs!
>>
>> Regards,
>> Joel
>
> Which is the glibc version, gcc, and binutils you have used? This symbol was
> removed by 118816de3383ff12769349784689141355cc787c (glibc 2.37), but I do
> recall something similar on old releases.
prev parent reply other threads:[~2024-04-17 16:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-16 15:23 Joel GUITTET
2024-04-17 12:18 ` Adhemerval Zanella Netto
2024-04-17 13:26 ` Joel GUITTET
2024-04-17 16:01 ` Adhemerval Zanella Netto [this message]
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=7a1a44fb-a825-4f99-abf5-af73bc2cbe97@linaro.org \
--to=adhemerval.zanella@linaro.org \
--cc=jguittet.opensource@witekio.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).