From: Ian Lance Taylor <ian@cygnus.com>
To: davem@caip.rutgers.edu
Cc: gas2@cygnus.com
Subject: Re: more on bfd assertion failures.
Date: Mon, 27 Nov 1995 23:00:00 -0000 [thread overview]
Message-ID: <9511280700.AA07388@tweedledumb.cygnus.com> (raw)
In-Reply-To: <199511280352.WAA02796@huahaga.rutgers.edu>
Date: Mon, 27 Nov 1995 22:52:09 -0500
From: "David S. Miller" <davem@caip.rutgers.edu>
The failure occurs in bfs/sunos.c:sunos_scan_ext_relocs() in the
following assertions:
BFD_ASSERT (r_type == RELOC_JMP_TBL
|| (h->flags & SUNOS_REF_REGULAR) != 0);
The sunos_link_hash_entry looks like
(gdb) p *h
$3 = {root = {root = {root = {next = 0x0, string = 0x6e290 "_pte_exprotect",
hash = 299445140}, type = bfd_link_hash_defined, next = 0x67aa8, u = {undef = {
abfd = 0x1cc}, def = {value = 460, section = 0x69c70}, i = {link = 0x1cc,
warning = 0x69c70 ""}, c = {size = 460, p = 0x69c70}}}, written = false,
indx = -1}, dynindx = -2, dynstr_index = -1, got_offset = 0, plt_offset = 0,
flags = 2 '\002'}
and r_type has the value '8'
I don't understand this. The value of SUNOS_REF_REGULAR is 2, so why
is the assertion failing?
Ian
prev parent reply other threads:[~1995-11-27 23:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1995-11-27 19:52 David S. Miller
1995-11-27 23:00 ` Ian Lance Taylor [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=9511280700.AA07388@tweedledumb.cygnus.com \
--to=ian@cygnus.com \
--cc=davem@caip.rutgers.edu \
--cc=gas2@cygnus.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).