From: Markus Wichmann <nullplan@gmx.net>
To: musl@lists.openwall.com
Subject: Re: dynamic linker command line invocation
Date: Mon, 4 Jan 2016 20:22:06 +0100 [thread overview]
Message-ID: <20160104192206.GB2016@debian> (raw)
In-Reply-To: <CAOkOUedcOLRBgmB7ez+bvdcau1g-86ymNHpOSU1AKD8ArqgWsA@mail.gmail.com>
On Mon, Jan 04, 2016 at 11:59:16AM -0500, N Jain wrote:
> Hi All,
>
> I am trying to add ldso functionality in my kernel. I am loading the
> dynamic linker "ld-musl-arm.so.1" into memory and passing the other
> application as command line which requires the dynamic libraries but the
> linker is generating fault during stage 2 "__dls2" at some random location
> 0x464cc57f.
>
Why don't you just set ld-musl-arm.so.1 as dynamic interpreter and
launch the application through the kernel? (Link with -Wl,-I,/lib/ld...)
> I am fairly new to dynamic linking code and trying to understand _dlstart_c
> code functionality. Can any one explain what are the command line arguments
> dynamic linker expects at this entry point ? I am giving numArgs = 1 and
> argv = app.elf after loading "ld-musl-arm.so.1" into memory ? Is this
> approach correct ? Do I have to also load app.elf into memory or the
> dynamic linker will take care of loading it ?
>
You say it's crashing stage 2, but only stage 3 handles arguments. In
any case, musl expects the application's ELF image in argv[1]. The rest
of argv is assumed to be the command line of the application. And
argv[0] is ignored, save for a comparison to "ldd" (if argv[0] ends in
"ldd", the dynlinker will just display all the loaded libraries).
> Thanks,
> NJ
Ciao,
Markus
next prev parent reply other threads:[~2016-01-04 19:22 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-04 16:59 N Jain
2016-01-04 19:22 ` Markus Wichmann [this message]
2016-01-04 20:52 ` Rich Felker
2016-01-04 20:59 ` Rich Felker
2016-01-05 16:45 ` N Jain
2016-01-05 17:32 ` Rich Felker
2016-01-05 18:00 ` N Jain
2016-01-05 18:23 ` Rich Felker
2016-01-07 23:29 ` N Jain
2016-01-08 11:09 ` Markus Wichmann
2016-01-11 17:03 ` N Jain
2016-01-12 16:24 ` Markus Wichmann
2016-01-14 22:30 ` Rich Felker
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=20160104192206.GB2016@debian \
--to=nullplan@gmx.net \
--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).