public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jan.kratochvil at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sources.redhat.com
Subject: [Bug libc/14166] invalid IFUNC DW_AT_linkage_name: memmove strstr time
Date: Wed, 08 Aug 2012 16:09:00 -0000	[thread overview]
Message-ID: <bug-14166-131-O2RdbDeIM2@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-14166-131@http.sourceware.org/bugzilla/>

http://sourceware.org/bugzilla/show_bug.cgi?id=14166

Jan Kratochvil <jan.kratochvil at redhat dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|WAITING                     |NEW
                 CC|                            |jan.kratochvil at redhat
                   |                            |dot com

--- Comment #2 from Jan Kratochvil <jan.kratochvil at redhat dot com> 2012-08-08 16:09:35 UTC ---
There should be no DWARF for memmove.
GDB should see just the ELF symbol (which is IFUNC).

There can be some DWARF for memmove but if it is it must have different name,
such as __GI_memmove or whatever.

-- 
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.


  parent reply	other threads:[~2012-08-08 16:09 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-24 19:56 [Bug libc/14166] New: " jan.kratochvil at redhat dot com
2012-08-08 13:55 ` [Bug libc/14166] " hjl.tools at gmail dot com
2012-08-08 15:53 ` hjl.tools at gmail dot com
2012-08-08 16:09 ` jan.kratochvil at redhat dot com [this message]
2012-08-08 17:52 ` hjl.tools at gmail dot com
2012-08-08 21:55 ` jan.kratochvil at redhat dot com
2012-08-10  6:01 ` jan.kratochvil at redhat dot com
2014-06-19 14:37 ` 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-14166-131-O2RdbDeIM2@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).