All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Hatle <mark.hatle@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: Re: Problem with new image-prelink
Date: Tue, 13 Sep 2011 19:52:22 -0500	[thread overview]
Message-ID: <4E6FFAC6.60404@windriver.com> (raw)
In-Reply-To: <1315905402.2519.116.camel@phil-desktop>

Please try the new version of the prelinker.  I just sent a pull request for it,
but there was a missing typecast on a printf.  This was causing problems on
various systems, and likely could be causing the issue that you observed on ARM
as well.

I did build the latest version for the ARM target, and successfully ran it there
under QEMU.

--Mark

On 9/13/11 4:16 AM, Phil Blundell wrote:
> On Tue, 2011-09-13 at 02:58 +0000, James Limbouris wrote:
>> root@192:~# gdb prelink
>> <...>
>> Reading symbols from /usr/sbin/prelink...Reading symbols from /usr/sbin/.debug/prelink...done.
>> done.
>> (gdb) set follow-fork-mode child
>> (gdb) run -a
>> Starting program: /usr/sbin/prelink -a
>> [New process 1712]
>> process 1712 is executing new program: /usr/sbin/prelink-rtld
>> [ 2777.370000] Alignment trap: prelink-rtld (1712) PC=0x410f9990 Instr=0xe5922024 Address=0x00000025 FSR 0x001
>>
>> Program received signal SIGBUS, Bus error.
>> [Switching to process 1712]
>> 0x410f9990 in __ctype_b_loc () at ../include/ctype.h:30
>> 30          *tablep = (const uint16_t *) _NL_CURRENT (LC_CTYPE, _NL_CTYPE_CLASS) + 128;
> 
> Just in case it's not obvious, the fact that this address is unaligned
> is the least of your worries.  Even if alignment didn't matter, you
> would just get a segfault instead since 0x25 is never going to be a
> valid pointer.
> 
> I guess you need to investigate where the value in r2 is coming from and
> figure out why it has this bogus value.
> 
> p.
> 
> 
> 
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core




  reply	other threads:[~2011-09-14  0:57 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-09  3:34 Problem with new image-prelink James Limbouris
2011-09-09 15:57 ` Mark Hatle
2011-09-12  1:39   ` James Limbouris
2011-09-12 14:50     ` Mark Hatle
2011-09-13  2:58       ` James Limbouris
2011-09-13  9:16         ` Phil Blundell
2011-09-14  0:52           ` Mark Hatle [this message]
2011-09-14  1:33             ` James Limbouris
2011-09-14 14:30               ` Mark Hatle
2011-09-15  1:01                 ` James Limbouris

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=4E6FFAC6.60404@windriver.com \
    --to=mark.hatle@windriver.com \
    --cc=openembedded-core@lists.openembedded.org \
    /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. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.