mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Gernot Reisinger <Gernot.Reisinger@omnino.at>
To: musl@lists.openwall.com
Subject: Question regarding dynamic loader
Date: Wed, 21 Nov 2018 14:55:19 +0100	[thread overview]
Message-ID: <CALsoeqnLKzNMdkEUtkevpG3Upgn6HFJMvESc+N=D796acTdA2g@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 823 bytes --]

Hi,
I recently stumbled upon an issue with preloading a shared object into a Go
application (see related Go ticket https://github.com/golang/go/issues/28909
).

In short - Go comes with an internal linker which will not link crt code to
the application. The entry point will directly execute Go standard library
code. As musl libc calls shared object constructors in crt code, the shared
objects constructors subsequently will never be invoked. Things will work
on glibc systems / processes. it It seems to be a subtle - but in this case
wide reaching - behavioral difference to glibc.

I wonder if calling constructor functions from crt code is an intended musl
libc behavior. My personal - non expert - gut feeling considers glibc
behavior "more correct". Is there a chance that musl will change this
behavior?
br
Gernot

[-- Attachment #2: Type: text/html, Size: 1013 bytes --]

             reply	other threads:[~2018-11-21 13:55 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-21 13:55 Gernot Reisinger [this message]
2018-11-21 14:25 ` Rich Felker
2018-11-21 15:52   ` Gernot Reisinger
2018-11-21 16:41     ` Szabolcs Nagy
2018-11-23 11:34       ` Gernot Reisinger
2018-11-21 16:14   ` Rich Felker
2018-11-21 14:46 ` Szabolcs Nagy
2018-11-23  9:29 ` Florian Weimer

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='CALsoeqnLKzNMdkEUtkevpG3Upgn6HFJMvESc+N=D796acTdA2g@mail.gmail.com' \
    --to=gernot.reisinger@omnino.at \
    --cc=musl@lists.openwall.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. 
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/musl/

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 NNTP newsgroup(s).