public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ma.jiang at zte dot com.cn" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug dynamic-link/16971] SEGV in do_sym
Date: Wed, 21 May 2014 09:20:00 -0000 [thread overview]
Message-ID: <bug-16971-131-4HdiHMFKMU@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-16971-131@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=16971
ma.jiang at zte dot com.cn changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|WAITING |RESOLVED
Resolution|--- |FIXED
--- Comment #3 from ma.jiang at zte dot com.cn ---
(In reply to ma.jiang from comment #2)
> (In reply to Andreas Schwab from comment #1)
> > Please provide a complete test case. I cannot reproduce that, there is
> > always at least _dl_main_map.
>
> I can use this code to reproduce the bug on MIPS(qemu).
>
> #include <dlfcn.h>
> #include <stdio.h>
> int main()
> {
>
> void *x = dlsym(NULL, "_r_debug");
> return 0;
> }
>
> I can reproduce this bug on glibc-2.13, currently I can not got a latest
> mips glibc. Sorry if this bug has got fixed elsewhere.
This bug is fixed in dl-support.c.
/* Namespace information. */
struct link_namespaces _dl_ns[DL_NNS] =
{
[LM_ID_BASE] =
{
._ns_loaded = &_dl_main_map,
._ns_nloaded = 1,
._ns_main_searchlist = &_dl_main_map.l_searchlist,
}
};
After adding the dummy link map, checking the match in do_sym is not
necessary.Sorry for the trouble I have make.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2014-05-21 9:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-16971-131@http.sourceware.org/bugzilla/>
2014-05-21 8:08 ` schwab@linux-m68k.org
2014-05-21 8:35 ` ma.jiang at zte dot com.cn
2014-05-21 9:20 ` ma.jiang at zte dot com.cn [this message]
2014-06-12 19:16 ` fweimer at redhat dot com
2014-06-12 19:16 ` fweimer at redhat dot com
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=bug-16971-131-4HdiHMFKMU@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=glibc-bugs@sourceware.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 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 read-only IMAP folder(s) and NNTP newsgroup(s).