All of lore.kernel.org
 help / color / mirror / Atom feed
From: amodra@one.net.au
To: Matthew Wilcox <matthew@wil.cx>
Cc: Paul Bame <bame@riverrock.org>,
	parisc-linux@parisc-linux.org, bame@www.riverrock.org
Subject: Re: [parisc-linux] More unaligned references
Date: Tue, 22 May 2001 10:37:40 +0930	[thread overview]
Message-ID: <20010522103740.L30444@squeak.one.net.au> (raw)
In-Reply-To: <20010521234050.J23718@parcelfarce.linux.theplanet.co.uk>; from matthew@wil.cx on Mon, May 21, 2001 at 11:40:50PM +0100

On Mon, May 21, 2001 at 11:40:50PM +0100, Matthew Wilcox wrote:
> On Mon, May 21, 2001 at 04:27:07PM -0600, Paul Bame wrote:
> > FYI in case others run across it, this was discovered to be the ".plt-1" bug.
> > To find out, use 'objdump -h' to figure out where .plt is loaded.  Then add
> > 0x4800 plus 0xfb plus the dp register (r27).  If that's .plt-1 you've found
> > the bug which is/should-be squashed in recent bits.
> 
> Not convinced.  Yes, this is in fact .plt-1.  However, that bug is
> supposed to be both fixed in this version of binutils and an assert
> added to catch it happening.  However, no assert is being tripped.
> FWIW, the offending caller is:
> 
>      1d0:       eb e0 00 00     b,l 1d8 <create_server_config+0x5c>,r31
>                         1d0: R_PARISC_PCREL17F  $$dyncall

A shared library created with the "bad" binutils exports millicode syms it
isn't supposed to, which the linker later rejects, resulting in .plt-1
references.  The assert should still have triggered...

A quick check whether a library is good is:
nm --dynamic <lib> | grep '\$\$'

This will show exported millicode syms since they start with '$$'.

Alan

      reply	other threads:[~2001-05-22  1:02 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-05-21 21:50 [parisc-linux] More unaligned references Matthew Wilcox
2001-05-21 22:27 ` Paul Bame
2001-05-21 22:40   ` Matthew Wilcox
2001-05-22  1:07     ` amodra [this message]

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=20010522103740.L30444@squeak.one.net.au \
    --to=amodra@one.net.au \
    --cc=bame@riverrock.org \
    --cc=bame@www.riverrock.org \
    --cc=matthew@wil.cx \
    --cc=parisc-linux@parisc-linux.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.