From: Andreas Schwab <schwab@linux-m68k.org>
To: Lanttor <lanttor.guo@freescale.com>
Cc: Maxim Kuvyrkov <maxim@codesourcery.com>,
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 20:23:28 +0100 [thread overview]
Message-ID: <m2fx4tnkgf.fsf@igel.home> (raw)
In-Reply-To: <4B8235FA.4050601@freescale.com> (Lanttor's message of "Mon, 22 Feb 2010 15:44:58 +0800")
Lanttor <lanttor.guo@freescale.com> writes:
> 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...
The assertion fails only if both l_libname and l_name are NULL.
Andreas.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
next prev parent reply other threads:[~2010-02-22 19:23 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
2010-02-22 19:23 ` Andreas Schwab [this message]
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=m2fx4tnkgf.fsf@igel.home \
--to=schwab@linux-m68k.org \
--cc=gerg@snapgear.com \
--cc=lanttor.guo@freescale.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox