From: Roland McGrath <roland@redhat.com>
To: Jakub Jelinek <jakub@redhat.com>
Cc: Andreas Jaeger <aj@suse.de>,
GNU libc hacker <libc-hacker@sources.redhat.com>
Subject: Re: problems with ctype...
Date: Mon, 16 Sep 2002 06:22:00 -0000 [thread overview]
Message-ID: <200209161203.g8GC3wa02139@magilla.sf.frob.com> (raw)
In-Reply-To: Jakub Jelinek's message of Monday, 16 September 2002 11:22:20 +0200 <20020916112220.C1013@sunsite.ms.mff.cuni.cz>
> Actually, looking at it again, what is in CVS doesn't work at all.
Works just fine for me.
> Just readelf -Wr libc.so | grep __ctype to find out.
You mean -Ws, no doubt. Here are just the __ctype_b matches in mine:
1721: 00021f98 114 FUNC GLOBAL DEFAULT 11 __ctype_b_loc@@GLIBC_2.3
2013: 00112a34 4 OBJECT GLOBAL DEFAULT 16 __ctype_b@GLIBC_2.0
3595: 00112a34 4 OBJECT LOCAL DEFAULT 16 __ctype_b
6681: 00021f98 114 FUNC GLOBAL DEFAULT 11 __ctype_b_loc
6973: 00112a34 4 OBJECT GLOBAL DEFAULT 16 __ctype_b@GLIBC_2.0
> If it was supposed to work, it would have to have __ctype_b@GLIBC_2.0
> (or __ctype_b@@GLIBC_2.0) etc. dynamic relocs.
??? Must be too early in the morning, else it's too late for me. There
are no relocs referring to these symbols because the references resolve
internally. There are dynamic symbol table entries as there should be.
next prev parent reply other threads:[~2002-09-16 13:22 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-15 20:55 Andreas Jaeger
2002-09-15 22:15 ` Roland McGrath
2002-09-15 23:52 ` Andreas Jaeger
2002-09-15 23:59 ` Roland McGrath
2002-09-16 0:01 ` Andreas Jaeger
2002-09-16 8:07 ` H. J. Lu
2002-09-16 21:54 ` Roland McGrath
2002-09-16 22:00 ` H. J. Lu
2002-09-16 0:01 ` Jakub Jelinek
2002-09-16 0:50 ` Andreas Jaeger
2002-09-16 2:22 ` Jakub Jelinek
2002-09-16 6:22 ` Roland McGrath [this message]
2002-09-16 8:04 ` H. J. Lu
2002-09-16 8:01 ` H. J. Lu
[not found] <20020916092949.A12870@devserv.devel.redhat.com>
2002-09-18 11:34 ` Roland McGrath
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=200209161203.g8GC3wa02139@magilla.sf.frob.com \
--to=roland@redhat.com \
--cc=aj@suse.de \
--cc=jakub@redhat.com \
--cc=libc-hacker@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).