From: Elena Zannoni <ezannoni@cygnus.com>
To: Joel Brobecker <brobecker@act-europe.fr>
Cc: Elena Zannoni <ezannoni@cygnus.com>, gdb-patches@sources.redhat.com
Subject: Re: [patch] Fix uninitialized section index internal error
Date: Wed, 27 Jun 2001 22:32:00 -0000 [thread overview]
Message-ID: <15162.49567.698243.168595@kwikemart.cygnus.com> (raw)
In-Reply-To: <20010615084043.E10731@act-europe.fr>
Joel Brobecker writes:
> Hi Elena,
>
> thank you very much for reviewing this patch.
>
> > I see what's happening, your symbol is in section scSBss and not in scBss.
> > This macro in mdebugread.c:
> > SC_IS_BSS(sc) ((sc) == scBss || (sc) == scSBss)
> >
> > evaluates to true, so you get to execute:
> >
> > else if (SC_IS_BSS (ext_in->asym.sc))
> > {
> > ms_type = mst_bss;
> > svalue += ANOFFSET (objfile->section_offsets, SECT_OFF_BSS (objfile));
> >
> > or (a few lines below):
> >
> > else if (SC_IS_BSS (ext_in->asym.sc))
> > {
> > ms_type = mst_file_bss;
> > svalue += ANOFFSET (objfile->section_offsets, SECT_OFF_BSS (objfile));
> > }
> >
> >
> > The SECT_OFF_BSS then is -1. It shouldn't be used in this case,
> > because the symbol may not be in the bss section.
> >
> > That said, may I suggest a different approach? I think the bug is
> > really in mdebugread.c, not symfile.c. I think the SC_IS_BSS macro
> > should be split in 2 separate ones: a proper SC_IS_BSS and another
> > SC_IS_SBSS for your case. Then the above code would work ok, if you
> > don't have the .bss section, because it wouldn't trigger. As for the
> > SC_IS_SBSS case, you would have to figure out what the correct value
> > to be added to svalue needs to be, and for this you need to find the
> > index of the .sbss section.
>
> Ok, our patch was based on the assumption that the .bss and .sbss
> sections were mutually exclusive. Your approach is more solid.
>
> May I suggest then to go a little further with your approach, which
> cries out for the addition of a new sect_index_sbss in the objfile
> structure:
> - in struct objfile (objfiles.h), add a new section index called
> sect_index_sbss
> - still in objfiles.h, add a new SECT_OFF_SBSS macro
> - initialize the sbss section index in default_symfile_offset
> (symfile.c) at the same time we're initializing the indexes of
> the other common sections
> - in mdebugread.c, fix the SC_IS_BSS macro, add a new SC_IS_SBSS
> macro, and then update the parse_partial_symbols () procedure
> to use the .sbss section if the symbol is there
>
> If you agree with this approach, I'll then submit the new patch.
Joel,
Sorry, but we are trying to move away from having gdb knowing that
some sections are special. Adding a new SECT_OFF_SBSS macro, would not
be in line with that. Would you mind just doing that bit I suggested?
That would solve your immediate problem, right?
Thanks a bunch
Elena
>
> Thanks,
> --
> Joel
>
next prev parent reply other threads:[~2001-06-27 22:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-10 14:40 Joel Brobecker
2001-06-12 14:18 ` Elena Zannoni
2001-06-14 23:40 ` Joel Brobecker
2001-06-27 22:32 ` Elena Zannoni [this message]
2001-06-28 5:23 ` Joel Brobecker
2001-06-28 20:17 ` Elena Zannoni
2001-11-06 7:40 ` Joel Brobecker
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=15162.49567.698243.168595@kwikemart.cygnus.com \
--to=ezannoni@cygnus.com \
--cc=brobecker@act-europe.fr \
--cc=gdb-patches@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