From: Florian Weimer <fw@deneb.enyo.de>
To: Lukasz Stelmach via Libc-alpha <libc-alpha@sourceware.org>
Cc: Lukasz Stelmach <l.stelmach@samsung.com>,
schwab@suse.de, maskray@google.com, fweimer@redhat.com,
palmer@dabbelt.com, adhemerval.zanella@linaro.org,
joseph@codesourcery.com, binutils@sourceware.org,
Marek Pikula <m.pikula@partner.samsung.com>,
Marek Szyprowski <m.szyprowski@samsung.com>,
Karol Lewandowski <k.lewandowsk@samsung.com>
Subject: Re: global pointer gets overwritten with dlopen(3) on RISC-V
Date: Fri, 12 May 2023 17:13:10 +0200 [thread overview]
Message-ID: <87wn1dfurd.fsf@mid.deneb.enyo.de> (raw)
In-Reply-To: <oypijda5y97hre.fsf%l.stelmach@samsung.com> (Lukasz Stelmach via Libc-alpha's message of "Fri, 12 May 2023 16:21:09 +0200")
* Lukasz Stelmach via Libc-alpha:
> We've got a program (the testee) written in C that we test with another
> one (a testing harness, the tester) written in C++ with gtest. So far,
> so good. To make the testing and inspection of the internal state of the
> testee easier the tester does not start the testee as a separate process
> but loads it with dlopen(3) and calls the testee's main() function.
We specifically disallow this in current glibc because it does not
work in general—unless the application is really loadable as a shared
object (compiled as PIC and linked with -shared).
next prev parent reply other threads:[~2023-05-12 15:13 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20230512142114eucas1p112d969a89ad2480a0c10a532bd6d8440@eucas1p1.samsung.com>
2023-05-12 14:21 ` Lukasz Stelmach
2023-05-12 15:13 ` Florian Weimer [this message]
2023-05-15 13:47 ` Palmer Dabbelt
[not found] ` <CGME20230516065316eucas1p17bffcd25209bb441b9a9f4d263aa8b3c@eucas1p1.samsung.com>
2023-05-16 6:53 ` Lukasz Stelmach
2023-05-16 7:59 ` Szabolcs Nagy
2023-05-17 0:11 ` Palmer Dabbelt
2023-05-12 19:50 ` Fangrui Song
2023-05-12 20:11 ` Florian Weimer
2023-05-12 20:33 ` Palmer Dabbelt
2023-05-12 21:09 ` Fangrui Song
2023-05-12 21:57 ` Palmer Dabbelt
2023-05-12 22:34 ` Fangrui Song
2023-05-12 22:47 ` Palmer Dabbelt
2023-05-13 0:05 ` Fangrui Song
2023-05-13 0:35 ` Palmer Dabbelt
2023-05-16 3:56 ` Fangrui Song
2023-05-16 22:51 ` Palmer Dabbelt
2023-05-16 23:21 ` Palmer Dabbelt
2023-05-12 20:35 ` Jeff Law
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=87wn1dfurd.fsf@mid.deneb.enyo.de \
--to=fw@deneb.enyo.de \
--cc=adhemerval.zanella@linaro.org \
--cc=binutils@sourceware.org \
--cc=fweimer@redhat.com \
--cc=joseph@codesourcery.com \
--cc=k.lewandowsk@samsung.com \
--cc=l.stelmach@samsung.com \
--cc=libc-alpha@sourceware.org \
--cc=m.pikula@partner.samsung.com \
--cc=m.szyprowski@samsung.com \
--cc=maskray@google.com \
--cc=palmer@dabbelt.com \
--cc=schwab@suse.de \
/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).