From: Jim Blandy <jimb@redhat.com>
To: Kevin Buettner <kevinb@redhat.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFA] symtab.c: Search section table when fixing up a symbol's section
Date: Mon, 17 May 2004 21:01:00 -0000 [thread overview]
Message-ID: <vt2n04693gv.fsf@zenia.home> (raw)
In-Reply-To: <20040517120219.5fad9bc0@saguaro>
Kevin Buettner <kevinb@redhat.com> writes:
> The patch below fixes all scope.exp failures for the frv-uclinux target.
>
> I believe that fixup_section() was broken for many other targets too,
> but innocuously so, since most targets relocate all sections (for a
> particular objfile) by a single constant. Thus, for those targets, it
> doesn't matter that fixup_section() incorrectly computes (or fails to
> compute) a symbol's section index. OTOH, the frv-uclinux target
> requires that the section index be accurately computed since read-only
> and read/write sections are relocated by different amounts. Other
> targets with this property (such as AIX) avoid the problem by making
> sure that the section value is set correctly by the symbol reader itself.
>
> Other details are included in a comment in the patch itself. (See
> below.)
>
> Thanks to Jim Blandy for suggesting the section table search. My
> first attempt at fixing this problem used a much less efficient
> search of the minimal symbols.
>
> Okay to commit?
Oh, endaddr *is* inclusive. Well done.
I'm going to leave this for others' comments for a few days, but other
than that, it looks good to me.
next prev parent reply other threads:[~2004-05-17 21:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-17 19:02 [RFA] symtab.c: Search section table when fixing up a symbol'ssection Kevin Buettner
2004-05-17 21:01 ` Jim Blandy [this message]
2004-05-17 21:23 ` Kevin Buettner
2004-05-18 6:15 ` [RFA] symtab.c: Search section table when fixing up a symbol's section Jim Blandy
2004-05-18 17:00 ` Jim Blandy
2004-05-24 16:12 ` [RFA] symtab.c: Search section table when fixing up a symbol'ssection Kevin Buettner
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=vt2n04693gv.fsf@zenia.home \
--to=jimb@redhat.com \
--cc=gdb-patches@sources.redhat.com \
--cc=kevinb@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