public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jengelh at inai dot de" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sources.redhat.com
Subject: [Bug libc/14376] glibc-2.16 strdup Illegal Instruction on sparc64
Date: Mon, 17 Sep 2012 21:15:00 -0000 [thread overview]
Message-ID: <bug-14376-131-IL1d5wYVY6@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-14376-131@http.sourceware.org/bugzilla/>
http://sourceware.org/bugzilla/show_bug.cgi?id=14376
--- Comment #9 from Jan Engelhardt <jengelh at inai dot de> 2012-09-17 21:15:24 UTC ---
binutils is 2.22, so objdump output should be accurate. I upgraded to
gdb-7.4.50.20120603 now so that it has also used the 2.22 tools during build.
(Previously gdb-7.1 was used.)
This changes things only minimally. __strdup has become __GI___strdup in gdb
printouts, but it still shows a call to _Qp_xtoq@plt+64 rather than memcpy in
the disassembly of (__GI___)strdup.
But I do not think gdb is at fault here - since the SIGILL also happens without
it. It seems as if the resolver is botched.
Calling memcpy() from in main() properly executes the memcpy function, i.e.
will call __memcpy_niagara1. The problem really only seems to affect references
to IFUNCs from within libc.so itself.
Login account could be provided, if you would want to have a peek at this.
--
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
next prev parent reply other threads:[~2012-09-17 21:15 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-20 10:25 [Bug libc/14376] New: " jengelh at medozas dot de
2012-07-20 10:26 ` [Bug libc/14376] " jengelh at medozas dot de
2012-07-20 10:35 ` aj at suse dot de
2012-07-20 10:43 ` aj at suse dot de
2012-07-24 1:38 ` davem at davemloft dot net
2012-07-24 1:43 ` carlos_odonell at mentor dot com
2012-09-17 8:15 ` jengelh at inai dot de
2012-09-17 8:24 ` jengelh at inai dot de
2012-09-17 9:58 ` jengelh at inai dot de
2012-09-17 16:18 ` davem at davemloft dot net
2012-09-17 16:29 ` davem at davemloft dot net
2012-09-17 21:15 ` jengelh at inai dot de [this message]
2012-09-28 4:25 ` davem at davemloft dot net
2012-09-28 7:01 ` jengelh at inai dot de
2012-09-28 7:20 ` davem at davemloft dot net
2014-06-17 18:57 ` 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-14376-131-IL1d5wYVY6@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=glibc-bugs@sources.redhat.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).