From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.org/gmane.linux.lib.musl.general/7065 Path: news.gmane.org!not-for-mail From: Rich Felker Newsgroups: gmane.linux.lib.musl.general Subject: Re: Executable crashes at __libc_start_main Date: Tue, 17 Feb 2015 10:46:56 -0500 Message-ID: <20150217154656.GE23507@brightrain.aerifal.cx> References: <54E29C2C.5080907@davidgf.es> 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 1424188049 18243 80.91.229.3 (17 Feb 2015 15:47:29 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Tue, 17 Feb 2015 15:47:29 +0000 (UTC) Cc: musl@lists.openwall.com To: David Guillen Original-X-From: musl-return-7078-gllmg-musl=m.gmane.org@lists.openwall.com Tue Feb 17 16:47:23 2015 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 1YNkMr-0004Bu-27 for gllmg-musl@m.gmane.org; Tue, 17 Feb 2015 16:47:21 +0100 Original-Received: (qmail 18196 invoked by uid 550); 17 Feb 2015 15:47:18 -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 18091 invoked from network); 17 Feb 2015 15:47:13 -0000 Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Original-Sender: Rich Felker Xref: news.gmane.org gmane.linux.lib.musl.general:7065 Archived-At: On Tue, Feb 17, 2015 at 09:20:38AM +0000, David Guillen wrote: > Hi, > > The toolchain is a "buildroot" one, so it _should_ be OK. The funny > think as I said is that it works well on some ARM boxes and qemu, so > it might be something related to the ld-linux.so. That code is not supposed to be compiled at all in shared libc, only static, and for static there is no "ld-linux". Also the dynamic linker should be ld-musl-arm.so.1; if it's using ld-linux that's a foreign dynamic linker that's not going to work. > Rich: R5 is OK, it points to the following 4 bytes (due to > postincrement), so I guess it must be OK before the load. And BTW I'm > not using thumb code, all instructions are ARM 32 bit wide > instructions. Sorry, I misread the address column as the instruction encoding when I saw just 4 hex digits. :-) So that's not the issue. Can you dump the address range for __init_array_start at runtime in gdb using the x command? Rich