All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lanttor <lanttor.guo@freescale.com>
To: Maxim Kuvyrkov <maxim@codesourcery.com>
Cc: Greg Ungerer <gerg@snapgear.com>, linux-m68k@vger.kernel.org
Subject: Re: One issue during kernel porting on coldfire m5441x: dl_main: Assertion `_rtld_local._dl_rtld_map.l_libname' failed!
Date: Mon, 22 Feb 2010 15:44:58 +0800	[thread overview]
Message-ID: <4B8235FA.4050601@freescale.com> (raw)
In-Reply-To: <4B8149BC.5020801@codesourcery.com>

Hi, Max

Thanks for your information.


> It is quite strange that the run-time linker is invoked for a
> statically linked busybox -- maybe this is the problem?
This is not the problem, because I setup udevd daemon before busybox
when boot up. when I disable udevd and use static dev files, there will
no error information.
That means staitic binary is OK to run, but if I run dynamic binary,
it's failed and prints log: Inconsistency detected by ld.so: rtld.c:
1215: dl_main: Assertion `_rtld_local._dl_rtld_map.l_libname' failed!

> I suggest you take a look at <glibc_src>/elf/rtld.c and trace how the
> control gets there.
I use glibc-2.5 and check elf/rtld.c 1215 line, the code is as follows:

1206   if (! GL(dl_rtld_map).l_libname && GL(dl_rtld_map).l_name)
1207     {
1208       /* We were invoked directly, so the program might not have a
1209          PT_INTERP.  */
1210       _dl_rtld_libname.name = GL(dl_rtld_map).l_name;
1211       /* _dl_rtld_libname.next = NULL;  Already zero.  */
1212       GL(dl_rtld_map).l_libname =  &_dl_rtld_libname;
1213     }
1214   else
1215     assert (GL(dl_rtld_map).l_libname); /* How else did we get
here?  */


So I guess GL(dl_rtld_map).l_libname is not NUL and throws an
exception.  The reason is still tracing...

Best Regards,
Lanttor




------------------------------------------------------------------------
*From:* Maxim Kuvyrkov <maxim@codesourcery.com>
*Sent:* 02/21/2010 10:57:00 PM +0800
*To:* Lanttor <lanttor.guo@freescale.com>
*CC:* Greg Ungerer <gerg@snapgear.com>, linux-m68k@vger.kernel.org
*Subject:* One issue during kernel porting on coldfire m5441x: dl_main:
Assertion `_rtld_local._dl_rtld_map.l_libname' failed!

> On 2/21/10 12:02 PM, Lanttor wrote:
>> Hi,
>>
>> I met one interesting issue during I porting 2.6.29 kernel on ColdFire
>> paltform (v4 core, mcf5441x).
>>
>> I could boot up the kernel with initramfs, but the kernel message below
>> displays some error information,
>> which line I colored red. initramfs image only includes busybox static
>> binary.
> ...
>> Inconsistency detected by ld.so: rtld.c: 1215: dl_main: Assertion
>> `_rtld_local._dl_rtld_map.l_libname' failed!
>> Inconsistency detected by ld.so: rtld.c: 1215: dl_main: Assertion
>> `_rtld_local._dl_rtld_map.l_libname' failed!
>
> The error is an assertion failure in GLIBC's runtime linker, it is not
> a kernel issue.  It is quite strange that the run-time linker is
> invoked for a statically linked busybox -- maybe this is the problem? 
> I suggest you take a look at <glibc_src>/elf/rtld.c and trace how the
> control gets there.
>
> Regards,
>

  parent reply	other threads:[~2010-02-22  7:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-21  9:02 One issue during kernel porting on coldfire m5441x: dl_main: Assertion `_rtld_local._dl_rtld_map.l_libname' failed! Lanttor
     [not found] ` <4B8149BC.5020801@codesourcery.com>
2010-02-22  7:44   ` Lanttor [this message]
2010-02-22 19:23     ` Andreas Schwab
2010-02-23  7:51       ` Lanttor

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=4B8235FA.4050601@freescale.com \
    --to=lanttor.guo@freescale.com \
    --cc=gerg@snapgear.com \
    --cc=linux-m68k@vger.kernel.org \
    --cc=maxim@codesourcery.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.
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.