mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Igmar Palsenberg <igmar@palsenberg.com>
To: musl@lists.openwall.com
Subject: Re: Executable crashes at __libc_start_main
Date: Tue, 17 Feb 2015 07:49:55 +0100 (CET)	[thread overview]
Message-ID: <alpine.LRH.2.11.1502170748400.20786@s1.palsenberg.com> (raw)
In-Reply-To: <54E29C2C.5080907@davidgf.es>


> Finally I got a core dump and the program crashes here:
> 
>     88c8:       e1550007        cmp     r5, r7
>     88cc:       2a000003        bcs     88e0 <__libc_start_main+0x1b0>
>     88d0:       e4953004        ldr     r3, [r5], #4
>     88d4:       e1a0e00f        mov     lr, pc
>     88d8:       e12fff13        bx      r3
>     88dc:       eafffff9        b       88c8 <__libc_start_main+0x198>
> 
> In the 88d8 instruction to be more exact. Seems that R3 is holding the
> value 0xc8000082!!! Where is that 0xC8 at the beginning comming from?
> The PC reported by the core dump is 0xc8000080 which I guess it's just
> the vlaue of R3 aligned to 4 byte boundary. R5 points to the right
> place, it's just the value loaded by the load. Could it be that
> something corrupts my ELF? Could it be the OS being really dumb at
> loading the ELF? It's a pretty old kernel, 2.6.21.

You're absolutely sure your toolchain is OK ? Hard to track issues like 
this are usually caused by a wrong toolchain, and ARM has some nice quirks 
when it comes to this.



	Igmar


  parent reply	other threads:[~2015-02-17  6:49 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-17  1:41 David Guillen Fandos
2015-02-17  4:21 ` Rich Felker
2015-02-17  6:49 ` Igmar Palsenberg [this message]
2015-02-17  9:20   ` David Guillen
2015-02-17 15:46     ` Rich Felker
2015-02-17 15:50       ` David Guillen
2015-02-17 17:31       ` David Guillen Fandos

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=alpine.LRH.2.11.1502170748400.20786@s1.palsenberg.com \
    --to=igmar@palsenberg.com \
    --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).