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: RFC: "set osabi"
Date: Fri, 27 Dec 2002 20:01:00 -0000	[thread overview]
Message-ID: <20021228035045.GA26100@nevyn.them.org> (raw)
In-Reply-To: <20021228034746.GA25677@nevyn.them.org>

On Fri, Dec 27, 2002 at 10:47:46PM -0500, Daniel Jacobowitz wrote:
> As promised.  I'm also looking for comments on this patch.  I know it needs
> documentation still; that's on hold for a moment because it would conflict
> with one of my other pending doc patches (since I want to put them in the
> same section).  I'll do the docs before committing this.
> 
> This patch implements:
>   - "set osabi"
>   - "show osabi"
>   - The concept of a "default OS ABI" which will be applied instead
>     of GDB_OSABI_UNKNOWN to an untagged binary.
> 
> It looks like this:
> 
> (gdb) show osabi
> The current OS ABI is "auto" (currently "GNU/Linux").
> The default OS ABI is "GNU/Linux".
> (gdb) set osabi
> Requires an argument. Valid arguments are auto, default, none, SVR4, DJGPP,
> NetWare, GNU/Linux.
> (gdb) set osabi SVR4
> (gdb) show osabi
> The current OS ABI is "SVR4".
> The default OS ABI is "GNU/Linux".
> (gdb) set osabi default
> (gdb) show osabi
> The current OS ABI is "GNU/Linux".
> The default OS ABI is "GNU/Linux".
> (gdb) set osabi auto
> (gdb) show osabi
> The current OS ABI is "auto" (currently "GNU/Linux").
> The default OS ABI is "GNU/Linux".
> 
> 
> Right now, it doesn't handle architectures refusing an OSABI terribly
> gracefully.  This doesn't bother me because:
>   - The logical place to handle this gracefully is clearly marked
>   - The interfaces to handle it are already there via gdbarch
>   - None of our architectures ever actually refuse an OSABI anyway as far
>     as I can see; they just treat unknowns as, well, unknown.  That needs
>     to change some day.
> We'll cross that bridge when we come to it.
> 
> Comments?  Tentatively I'll apply this in a week or so, after I get feedback
> on the preceding patch (which this requires).

Oh, forgot to mention: as Andrew asked the last time this came up, "set
osabi" does correctly update the architecture immediately.

-- 
Daniel Jacobowitz
MontaVista Software                         Debian GNU/Linux Developer


  reply	other threads:[~2002-12-28  3:49 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-27 19:49 Daniel Jacobowitz
2002-12-27 20:01 ` Daniel Jacobowitz [this message]
2002-12-28  4:39 ` Mark Kettenis
2003-01-04 23:49 ` Daniel Jacobowitz
2003-01-05  2:05   ` Daniel Jacobowitz
2003-01-05  4:28     ` Eli Zaretskii
2003-01-05  4:35       ` Daniel Jacobowitz

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=20021228035045.GA26100@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