From: "H. J. Lu" <hjl@lucon.org>
To: Earl Chew <earl_chew@agilent.com>, gdb@sources.redhat.com
Subject: Re: Mystified by "Internal error: pc 0x89f21e10 read in psymtab, but not in symtab
Date: Sun, 15 Sep 2002 13:39:00 -0000 [thread overview]
Message-ID: <20020915133938.B19112@lucon.org> (raw)
In-Reply-To: <20020915160306.GA31994@nevyn.them.org>; from drow@mvista.com on Sun, Sep 15, 2002 at 12:03:06PM -0400
On Sun, Sep 15, 2002 at 12:03:06PM -0400, Daniel Jacobowitz wrote:
>
>
> My first suspect:
> 2001-10-23 Jim Blandy <jimb@redhat.com>
>
> Isolate STABS readers' use of the `textlow' and `texthigh' fields
> of `struct partial_symtab' to only a few locations. This change
> is not supposed to affect the way the values are computed, only
> where they live.
>
> * dbxread.c (struct symloc): Add `textlow' and `texthigh' fields
> to the reader-specific structure.
> * mdebugread.c (struct symloc): Same.
> * dbxread.c (TEXTLOW, TEXTHIGH): New accessor macros.
> * mdebugread.c (TEXTLOW, TEXTHIGH): Same.
> * dbxread.c (dbx_symfile_read): After we've built all our partial
> symbol tables, set each partial symtab's `textlow' and `texthigh'
> fields from our reader-specific structure.
> * mdebugread.c (mdebug_build_psymtabs): Same.
> * dbxread.c (start_psymtab): Initialize the reader-specific
> structure's `textlow' and `texthigh' from the new psymtab's.
> * mdebugread.c (parse_partial_symbols, new_psymtab): Same.
> * dbxread.c (read_dbx_symtab, end_psymtab, read_ofile_symtab): Use
> the reader-specific `textlow' and `texthigh', not the generic
> psymtab fields.
> * mdebugread.c (parse_lines, parse_partial_symbols,
> psymtab_to_symtab_1): Same.
> * partial-stab.h: Same.
>
> I no longer remember what Jim was trying to accomplish with this
> change, but it sounds like you're on the right track. You might want
> to see if this patch is causing the problem.
>
>
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.
H.J.
next prev parent reply other threads:[~2002-09-15 20:39 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 [this message]
2002-09-15 13:43 ` Daniel Jacobowitz
2002-09-15 21:42 ` Earl Chew
2002-09-16 7:03 ` H. J. Lu
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=20020915133938.B19112@lucon.org \
--to=hjl@lucon.org \
--cc=earl_chew@agilent.com \
--cc=gdb@sources.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