From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.org/gmane.linux.lib.musl.general/9113 Path: news.gmane.org!not-for-mail From: Rich Felker Newsgroups: gmane.linux.lib.musl.general Subject: Re: dynamic linker command line invocation Date: Thu, 14 Jan 2016 17:30:55 -0500 Message-ID: <20160114223055.GV238@brightrain.aerifal.cx> References: <20160104205920.GW238@brightrain.aerifal.cx> <20160105173200.GZ238@brightrain.aerifal.cx> <20160105182326.GB238@brightrain.aerifal.cx> <20160108110954.GC2016@debian> <20160112162402.GJ2016@debian> Reply-To: musl@lists.openwall.com NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: ger.gmane.org 1452810671 18638 80.91.229.3 (14 Jan 2016 22:31:11 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Thu, 14 Jan 2016 22:31:11 +0000 (UTC) To: musl@lists.openwall.com Original-X-From: musl-return-9126-gllmg-musl=m.gmane.org@lists.openwall.com Thu Jan 14 23:31:11 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 1aJqQA-0004bS-Ht for gllmg-musl@m.gmane.org; Thu, 14 Jan 2016 23:31:10 +0100 Original-Received: (qmail 12081 invoked by uid 550); 14 Jan 2016 22:31:08 -0000 Mailing-List: contact musl-help@lists.openwall.com; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-ID: Original-Received: (qmail 12058 invoked from network); 14 Jan 2016 22:31:08 -0000 Content-Disposition: inline In-Reply-To: <20160112162402.GJ2016@debian> User-Agent: Mutt/1.5.21 (2010-09-15) Original-Sender: Rich Felker Xref: news.gmane.org gmane.linux.lib.musl.general:9113 Archived-At: On Tue, Jan 12, 2016 at 05:24:02PM +0100, Markus Wichmann wrote: > On Mon, Jan 11, 2016 at 12:03:37PM -0500, N Jain wrote: > > Hi Marcus, > > > > Thanks. I am able to get this part working. > > I am facing one more issue during dynamic linking and need some help to > > understand how to resolve it. > > > > In below code part of __dls3 function I found that TPIDRURO register is > > being used to read the threadId. > > I would like to understand how kernel should set this value ? > > > > It shouldn't. musl calls __set_thread_area() (in __init_tp()), and that > has to set this register. Yes. The syscall made by __set_thread_area (it's an ARM-private syscall on ARM, for no good reason, rather than actually being SYS_set_thread_area) is supposed to set TPIDRURO for the calling thread to the address provided by the caller. Rich