From: Florian Weimer <fweimer@redhat.com>
To: Nima Hamidi via Libc-help <libc-help@sourceware.org>
Cc: Nima Hamidi <nimaa.hamidi@gmail.com>
Subject: Re: Using dlmope/dlopem with RTLD_GLOBAL
Date: Mon, 13 Feb 2023 11:29:55 +0100 [thread overview]
Message-ID: <87v8k5g8nw.fsf@oldenburg.str.redhat.com> (raw)
In-Reply-To: <052bc685-e6bb-4fbb-a696-f6810bdab1f6@Spark> (Nima Hamidi via Libc-help's message of "Mon, 13 Feb 2023 03:23:26 -0600")
* Nima Hamidi via Libc-help:
> The error won’t happen if I dlopen with RTLD_LOCAL in b.cpp rather
> than RTLD_GLOBAL. I would appreciate any help on what I’m doing wrong
> here.
I think I see what's going on. The add_to_global_resize function does
not take into account that the global scope does not exist yet when it
is called. Would you please file a bug in Bugzilla?
<https://sourceware.org/bugzilla/enter_bug.cgi?product=glibc&component=dynamic-link>
Thanks,
Florian
next prev parent reply other threads:[~2023-02-13 10:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <14297fb9-70cb-42b1-a477-6fb68c03ff64@Spark>
2023-02-13 9:23 ` Nima Hamidi
2023-02-13 10:29 ` Florian Weimer [this message]
2023-02-13 10:40 ` Nima Hamidi
2023-02-13 11:28 ` Nima Hamidi
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=87v8k5g8nw.fsf@oldenburg.str.redhat.com \
--to=fweimer@redhat.com \
--cc=libc-help@sourceware.org \
--cc=nimaa.hamidi@gmail.com \
/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).