From: Andrew Cagney <ac131313@redhat.com>
To: Daniel Jacobowitz <drow@mvista.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [commit] New function gdbarch_infi_fill
Date: Tue, 11 Nov 2003 18:42:00 -0000 [thread overview]
Message-ID: <3FB12DA6.2050201@redhat.com> (raw)
In-Reply-To: <20031110162644.GA28489@nevyn.them.org>
> 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.
Like with "frame_id", it would mean adding some sort of "special" field.
That way the MIPS could record that its debugging "o64" but with
variation #28: sizeof(long) == 8, FPU :-/
It would also make architecture creation more robust vis:
- fill in "gdbarch_info"
Setting osabi et.al. based on the bfd et.al.
- create the architecture from "gdbarch_info"
but with _no_ bfd.
harder to get right, but probably more correct.
Adding to wish list ...
Andrew
prev parent reply other threads:[~2003-11-11 18:42 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
2003-11-11 18:42 ` Andrew Cagney [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=3FB12DA6.2050201@redhat.com \
--to=ac131313@redhat.com \
--cc=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