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: [RFA] mips-tdep.c: Make ``show mips abi'' more useful
Date: Wed, 26 Feb 2003 03:10:00 -0000	[thread overview]
Message-ID: <20030226031021.GB1322@nevyn.them.org> (raw)
In-Reply-To: <1030226024118.ZM14581@localhost.localdomain>

On Tue, Feb 25, 2003 at 07:41:19PM -0700, Kevin Buettner wrote:
> By default, the command ``show mips abi'' will print the following:
> 
>     The ABI used by this program is "auto".
> 
> This information is not as useful as it could be.  In such cases, it
> would also be nice to know what GDB has determined the actual ABI to
> be.  The patch below adds a callback to augment the information provided
> by the ``show mips abi command''.  E.g,
> 
>     (gdb) file hello-n64-shared
>     Reading symbols from hello-n64-shared...done.
>     (gdb) show mips abi
>     The ABI used by this program is "auto".
>     Current ABI is "n64".
> 
> Okay?
> 
> (BTW, ``show language'' and some other commands in language.c use a
> similar mechanism for providing additional information.  It might
> be cleaner though to implement ``show mips abi'' in a fashion similar
> to the way that ``show osabi'' is implemented.)

I get the impression we need a standard mechanism for this sort of
variable - they just keep cropping up all over the place.

-- 
Daniel Jacobowitz
MontaVista Software                         Debian GNU/Linux Developer


  reply	other threads:[~2003-02-26  3:10 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-26  2:41 Kevin Buettner
2003-02-26  3:10 ` Daniel Jacobowitz [this message]
2003-02-26 21:29 ` Andrew Cagney
     [not found]   ` <mailpost.1046294979.10353@news-sj1-1>
2003-02-26 22:32     ` cgd
2003-02-26 23:04       ` Andrew Cagney
2003-02-27  1:33   ` Kevin Buettner
2003-02-27  2:18     ` 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=20030226031021.GB1322@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