From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.org/gmane.linux.lib.musl.general/9050 Path: news.gmane.org!not-for-mail From: N Jain Newsgroups: gmane.linux.lib.musl.general Subject: dynamic linker command line invocation Date: Mon, 4 Jan 2016 11:59:16 -0500 Message-ID: Reply-To: musl@lists.openwall.com NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: multipart/alternative; boundary=001a113d70a08c38780528850ad7 X-Trace: ger.gmane.org 1451926780 26330 80.91.229.3 (4 Jan 2016 16:59:40 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Mon, 4 Jan 2016 16:59:40 +0000 (UTC) To: musl@lists.openwall.com Original-X-From: musl-return-9063-gllmg-musl=m.gmane.org@lists.openwall.com Mon Jan 04 17:59:40 2016 Return-path: Envelope-to: gllmg-musl@m.gmane.org Original-Received: from mother.openwall.net ([195.42.179.200]) by plane.gmane.org with smtp (Exim 4.69) (envelope-from ) id 1aG8To-0005Rv-IP for gllmg-musl@m.gmane.org; Mon, 04 Jan 2016 17:59:36 +0100 Original-Received: (qmail 30506 invoked by uid 550); 4 Jan 2016 16:59:28 -0000 Mailing-List: contact musl-help@lists.openwall.com; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: Original-Received: (qmail 30487 invoked from network); 4 Jan 2016 16:59:28 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=C5LnMGJZZzu6DR/a1Qz+ImtstrHdR/iOq2DcCblXW8I=; b=ZtVZzfZoktAf+flxY5iYsCUT9axsNYNXwCsP4+K4lt7GHskthnRN+ste9qWVB5UDKO 5fhrMU3RhJJELI6NcaKnVGYvAitzU1ed+ExzKNIl6/4crzjsEWkGYCCE8WCe4Uo7wpXd 1dgFAbP62vRfgy+dieyWtVU1bGbXksjLQs/e/NTiw7vE7leWZMAtLfK0bJHidDLH11Uf sJq8lmXFS1lMA3WFZAhSjuTKCLTICR58Oqw1Nzy2PCvCxo30HvMXsIrdU0AsNiRNIySz mvLzzvEib0/wc0oupA9WZ1ffJ7hJdiOgUHaaFwznaoGHorjbGwO7JBaXtBfJuZM/8bI7 evwQ== X-Received: by 10.202.79.5 with SMTP id d5mr54364312oib.121.1451926756274; Mon, 04 Jan 2016 08:59:16 -0800 (PST) Xref: news.gmane.org gmane.linux.lib.musl.general:9050 Archived-At: --001a113d70a08c38780528850ad7 Content-Type: text/plain; charset=UTF-8 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. 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 ? Thanks, NJ --001a113d70a08c38780528850ad7 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hi All,

I am trying to add ldso functio= nality 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 st= age 2 "__dls2" at some random location 0x464cc57f.

=
I am fairly new to dynamic linking code and trying to understand= _dlstart_c code functionality. Can any one explain what are the command li= ne arguments dynamic linker expects at this entry point ? I am giving numAr= gs =3D 1 and argv =3D app.elf after loading "ld-musl-arm.so.1" in= to 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 ?

<= /div>
Thanks,
NJ


--001a113d70a08c38780528850ad7--