From: "H. J. Lu" <hjl@lucon.org>
To: Earl Chew <earl_chew@agilent.com>
Cc: gdb@sources.redhat.com, drow@mvista.com, jimb@redhat.com
Subject: Re: Mystified by "Internal error: pc 0x89f21e10 read in psymtab, but not in symtab
Date: Mon, 16 Sep 2002 07:03:00 -0000 [thread overview]
Message-ID: <20020916070335.A1149@lucon.org> (raw)
In-Reply-To: <3D85614B.8010701@agilent.com>; from earl_chew@agilent.com on Sun, Sep 15, 2002 at 09:42:51PM -0700
On Sun, Sep 15, 2002 at 09:42:51PM -0700, Earl Chew wrote:
> H. J. Lu wrote:
> > That patch is broken. See
> >
> > http://sources.redhat.com/ml/gdb/2002-03/msg00197.html
> > http://sources.redhat.com/ml/gdb/2002-03/msg00202.html
> >
> > Unfortunately, no one seems to care.
>
> I care, I care!
>
> How eerie. I wrote a set of changes this morning, and now comparing
> with your changes --- it's uncanny how close they are.
>
> I enclose my patches below for you to peruse. I have some questions
> regarding some minor differences:
>
> a. I figured it was better in general to invoke the relocation function
> pointer with the section offset structure, and let each
> implementation figure out what relocations are required. I
> thought that some implementations (in the future) might cache
> things other than text locations (eg data locations).
I don't think it helps since objfile_relocate only does offset. If you
pass delta, it is no longer symmetric. You don't want to use the same
function to do more than one thing here. You can always change it
together when you modify objfile_relocate later.
>
> b. In dbxread.c, I initialise the relocate_symtab pointer in
> start_psymtab _and_ end_psymtab (where the code loops and allocates
> new psymtabs and copies values across).
>
> Your patch doesn't initialise the function pointer here, and I
> believe that this will result in an uninitialised field.
I might miss that one.
H.J.
next prev parent reply other threads:[~2002-09-16 14:03 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-13 14:42 Earl Chew
2002-09-13 15:01 ` Daniel Jacobowitz
2002-09-13 15:42 ` Earl Chew
2002-09-13 15:51 ` Daniel Jacobowitz
2002-09-13 16:13 ` Earl Chew
2002-09-13 18:32 ` Daniel Jacobowitz
2002-09-15 8:43 ` Earl Chew
2002-09-15 9:02 ` Daniel Jacobowitz
2002-09-15 9:11 ` Earl Chew
2002-09-15 13:39 ` H. J. Lu
2002-09-15 13:43 ` Daniel Jacobowitz
2002-09-15 21:42 ` Earl Chew
2002-09-16 7:03 ` H. J. Lu [this message]
2002-09-16 12:26 ` Jim Blandy
2002-09-16 13:01 ` Earl Chew
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=20020916070335.A1149@lucon.org \
--to=hjl@lucon.org \
--cc=drow@mvista.com \
--cc=earl_chew@agilent.com \
--cc=gdb@sources.redhat.com \
--cc=jimb@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