Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@mvista.com>
To: gdb-patches@sources.redhat.com
Subject: Re: [commit/RFC/multiarch/hpux] HPUX_ELF osabi init routine incorrectly registered
Date: Thu, 14 Aug 2003 02:01:00 -0000	[thread overview]
Message-ID: <20030814020133.GA26416@nevyn.them.org> (raw)
In-Reply-To: <20030814003222.GK971@gnat.com>

On Wed, Aug 13, 2003 at 05:32:22PM -0700, Joel Brobecker wrote:
> Hello,
> 
> I noticed while working on the hppa64 target that the HPUX_ELF gdbarch
> initialization routine was not called during the gdbarch initialization.
> It turns out that we where using the default bfd arch_info descriptor
> which corresponds to a 32bit ABI. So when we checked the compatibility
> between the arch_info that we registered and the arch_info determined by
> the sniffer, we determined that they do not match, and therefore did not
> call the assiocated initialization routine.
> 
> I fixed the problem the best way I can, by using a hard-coded number
> corresponding to the arch_info that corresponds to hppa2.0w. I don't
> know BFD too well yet, but it looks like we should really be defining
> new #defines in archures.c for each hppa machine numbers, and then use
> them here instead of my hard-coded value. I added a FIXME to remind us,
> and will send a patch to binutils shortly. In them meantime, this fixes
> the problem.
> 
> Any opinions, maybe?

Seems right to me, on all counts.  But would you mind sending the BFD
patch first and then using the machine #define in GDB?  It's just a
matter of adding the define and regenerating bfd-in2.h.

-- 
Daniel Jacobowitz
MontaVista Software                         Debian GNU/Linux Developer


      reply	other threads:[~2003-08-14  2:01 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-14  0:32 Joel Brobecker
2003-08-14  2:01 ` Daniel Jacobowitz [this message]

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=20030814020133.GA26416@nevyn.them.org \
    --to=drow@mvista.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