Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Thiemo Seufer <ica2_ts@csv.ica.uni-stuttgart.de>
To: Joel Brobecker <brobecker@gnat.com>
Cc: binutils@sources.redhat.com, gdb-patches@sources.redhat.com
Subject: Re: [RFA] MIPS_TEXT symbols should be associated to .text section?
Date: Thu, 29 Jul 2004 22:19:00 -0000	[thread overview]
Message-ID: <20040729221904.GT965@rembrandt.csv.ica.uni-stuttgart.de> (raw)
In-Reply-To: <20040729220156.GK1167@gnat.com>

Joel Brobecker wrote:
> Hello BFD maintainers,
> 
> Ping? This patch is only 8 days old, and I wouldn't send a reminder
> just a week after sending it, but GDB is completely broken without
> this patch (ie "break main; run" doesn't work)... Would somebody mind
> having a look at it and tell me if it is good or not?
[snip]
> > @@ -4192,6 +4192,20 @@ _bfd_mips_elf_symbol_processing (bfd *ab
> >        asym->section = bfd_und_section_ptr;
> >        break;
> >  
> > +    case SHN_MIPS_TEXT:
> > +      { 
> > +        asection *section = bfd_get_section_by_name (abfd, ".text");
> > +        if (section != NULL)
> > +          {
> > +            asym->section = section;
> > +            /* MIPS_TEXT is a bit special, the address is not an offset
> > +               to the base of the .text section.  So substract the section
> > +               base address to make it an offset.  */
> > +	    asym->value -= section->vma;
> > +          }
> > +        break;
> > +      }
> > +    
> >  #if 0 /* for SGI_COMPAT */
> >      case SHN_MIPS_TEXT:
> >        asym->section = mips_elf_text_section_ptr;

The last three lines in this patch suggest AFAICS to use
mips_elf_text_section_ptr instead of bfd_get_section_by_name,
and to make the test conditional on SGI_COMPAT. The SHN_MIPS_DATA
below should probably get handled similiarily.


Thiemo


  reply	other threads:[~2004-07-29 22:19 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-21 20:46 Joel Brobecker
2004-07-29 22:02 ` Joel Brobecker
2004-07-29 22:19   ` Thiemo Seufer [this message]
2004-07-29 23:15     ` Mark Kettenis
2004-07-30  0:31       ` Thiemo Seufer
2004-07-30 11:32         ` Eli Zaretskii
2004-07-30 13:37           ` Andrew Cagney
2004-07-30 18:04             ` Eli Zaretskii
2004-07-30 18:13               ` Joel Brobecker
2004-07-30 18:44                 ` Eli Zaretskii
2004-07-30 18:55                   ` Joel Brobecker
2004-07-30 19:36                     ` Eli Zaretskii
2004-07-30 19:59                     ` Andrew Cagney
2004-07-30 22:29                     ` Michael Chastain
2004-07-30 18:08         ` Joel Brobecker
2004-07-30 18:57           ` Thiemo Seufer
2004-07-30 21:08             ` Mark Kettenis
2004-07-30 23:03             ` Joel Brobecker
2004-07-30 23:57               ` Thiemo Seufer
2004-07-30 18:19         ` Joel Brobecker
2004-07-30  0:17     ` Joel Brobecker
2004-07-22 15:47 David Anderson

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=20040729221904.GT965@rembrandt.csv.ica.uni-stuttgart.de \
    --to=ica2_ts@csv.ica.uni-stuttgart.de \
    --cc=binutils@sources.redhat.com \
    --cc=brobecker@gnat.com \
    --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