From: Kevin Buettner <kevinb@cygnus.com>
To: Daniel Berlin <dberlin@redhat.com>, Richard Henderson <rth@redhat.com>
Cc: gdb@sources.redhat.com
Subject: Re: [crash] Section index is uninitialized
Date: Thu, 30 Nov 2000 21:41:00 -0000 [thread overview]
Message-ID: <1001201054052.ZM7363@ocotillo.lan> (raw)
In-Reply-To: <m3wvdk21xf.fsf@dan2.cygnus.com>
On Nov 30, 11:36pm, Daniel Berlin wrote:
> > 4184 SYMBOL_VALUE_ADDRESS (sym) +=
> > (top-gdb) p *sym
> > $1 = {ginfo = {name = 0x1206e18f0 "_ZTIP1D", value = {ivalue = 4831863968,
> > block = 0x1200064a0, bytes = 0x1200064a0 "\206\002",
> > address = 4831863968, chain = 0x1200064a0}, language_specific = {
> > cplus_specific = {demangled_name = 0x0}, chill_specific = {
> > demangled_name = 0x0}}, language = language_cplus, section =-1, ^^
>
> That's the problem.
> Why it happens, no idea.
>
> If it helps, Kevin, we never set SYMBOL_SECTION in dwarf2read.
>
> Should we be setting it?
> We set it in stabsread.
The call to fixup_symbol_section() (which is one line before the line
indicated above) should be setting section to the section associated
with the minimal symbol. I think we need to find out why
fixup_symbol_section() is failing to do this. (Obviously, it could be
failing if if fails to locate the minimal symbol. If this is the
case, we need to find out if symbol simply doesn't exist in the minimal
symbol table or if it's a demangling problem... Or possibly there's
another reason why the symbol wouldn't be found.)
Kevin
next prev parent reply other threads:[~2000-11-30 21:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-30 17:41 Richard Henderson
2000-11-30 20:36 ` Daniel Berlin
2000-11-30 21:41 ` Kevin Buettner [this message]
2000-11-30 23:26 ` Richard Henderson
2000-12-01 0:51 ` Kevin Buettner
2000-12-01 1:35 ` Richard Henderson
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=1001201054052.ZM7363@ocotillo.lan \
--to=kevinb@cygnus.com \
--cc=dberlin@redhat.com \
--cc=gdb@sources.redhat.com \
--cc=rth@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).