From: "David S. Miller" <davem@davemloft.net>
To: roland@redhat.com
Cc: libc-hacker@sources.redhat.com
Subject: Re: check-textrel
Date: Thu, 02 Mar 2006 05:16:00 -0000 [thread overview]
Message-ID: <20060301.211611.35674120.davem@davemloft.net> (raw)
In-Reply-To: <20060302044154.191FB180B1B@magilla.sf.frob.com>
From: Roland McGrath <roland@redhat.com>
Date: Wed, 1 Mar 2006 20:41:54 -0800 (PST)
> > This turns out to be the .tdata section.
> >
> > LOAD off 0x0014e478 vaddr 0x0015e478 paddr 0x0015e478 align 2**16
> > filesz 0x00004984 memsz 0x00007268 flags rwx
> > ...
> > 17 .tdata 00000008 0015e478 0015e478 0014e478 2**2
> > CONTENTS, ALLOC, LOAD, DATA, THREAD_LOCAL
> >
> > Probably some binutils issue?
>
> That should be PT_TLS, not PT_LOAD.
Ok, my binutils was a little crufty, I'm retesting with current
binutils.
Thanks.
next prev parent reply other threads:[~2006-03-02 5:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-02 4:11 check-textrel David S. Miller
2006-03-02 4:42 ` check-textrel Roland McGrath
2006-03-02 5:16 ` David S. Miller [this message]
2006-03-02 6:12 ` check-textrel David S. Miller
2006-03-02 7:41 ` check-textrel Jakub Jelinek
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=20060301.211611.35674120.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=libc-hacker@sources.redhat.com \
--cc=roland@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).