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] New function gdbarch_infi_fill
Date: Mon, 10 Nov 2003 16:26:00 -0000	[thread overview]
Message-ID: <20031110162644.GA28489@nevyn.them.org> (raw)
In-Reply-To: <3FAFBA79.9060102@redhat.com>

On Mon, Nov 10, 2003 at 11:19:05AM -0500, Andrew Cagney wrote:
> >On Sun, Nov 09, 2003 at 06:50:54PM -0500, Andrew Cagney wrote:
> >
> >>Hello,
> >>
> >>The attached adds the new function gdbarch_info_fill.  This new function 
> >>fills in un-initialized fields of the "info" structure using global 
> >>"set" variables and the "gdbarch" parameter.
> >>
> >>committed,
> >>Andrew
> >
> >
> >Yeah!  I've wanted this before.  Though now I can't remember why.
> 
> This all begs two questions.
> 
> Should gdbarch_info be filled in first?

Not sure.

> Should the assertion:
> 
> 	gdbarch_find_by_info (gdbarch_info (gdbarch)) == gdbarch
> 
> always hold?  At present architectures like the MIPS make this very hard 
>  - keying off information found in the BFD and not the corresponding 
> info struct.

This, however, I'd really like.  I remember why I wanted it now.  Take
a look at the end of osabi.c:set_osabi - I am not especially confident
that that code works.  It seems to me that the above assertion makes it
much more likely to work.

-- 
Daniel Jacobowitz
MontaVista Software                         Debian GNU/Linux Developer


  reply	other threads:[~2003-11-10 16:26 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-09 23:52 Andrew Cagney
2003-11-10  0:48 ` Daniel Jacobowitz
2003-11-10 16:19   ` Andrew Cagney
2003-11-10 16:26     ` Daniel Jacobowitz [this message]
2003-11-11 18:42       ` Andrew Cagney

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=20031110162644.GA28489@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