Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Richard Earnshaw <rearnsha@arm.com>
To: Andrew Cagney <ac131313@cygnus.com>
Cc: Eli Zaretskii <eliz@is.elta.co.il>,
	Richard.Earnshaw@arm.com, gdb@sources.redhat.com
Subject: Re: Multi-arch and user-control of architecture flags
Date: Wed, 15 May 2002 07:11:00 -0000	[thread overview]
Message-ID: <200205151411.PAA23686@cam-mail2.cambridge.arm.com> (raw)
In-Reply-To: Your message of "Wed, 15 May 2002 10:04:10 EDT." <3CE26ADA.4050007@cygnus.com>


ac131313@cygnus.com said:
> Have a look at the ``(gdb) set mips'' command ;-)  Another group with
> the same problem are the ``info'' commands. 

Hmm, yep, that looks like what I want.

Note, however, there's something odd here...

  /* Add root prefix command for all "set mips"/"show mips" commands */
  add_prefix_cmd ("mips", no_class, set_mips_command,
                  "Various MIPS specific commands.",
                  &setmipscmdlist, "set mips ", 0, &setlist);

  add_prefix_cmd ("mips", no_class, show_mips_command,
                  "Various MIPS specific commands.",
                  &showmipscmdlist, "show mips ", 0, &showlist);

Then at the end of the file:

  /* Debug this files internals. */
  add_show_from_set (add_set_cmd ("mips", class_maintenance, var_zinteger,
                                  &mips_debug, "Set mips debugging.\n\
When non-zero, mips specific debugging is enabled.", &setdebuglist),
                     &showdebuglist);

One of these must shadow the other....

R.


  reply	other threads:[~2002-05-15 14:11 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-15  2:32 Richard Earnshaw
2002-05-15  3:23 ` Eli Zaretskii
2002-05-15  7:04   ` Andrew Cagney
2002-05-15  7:11     ` Richard Earnshaw [this message]
2002-05-15  7:21       ` Andrew Cagney
2002-05-16  6:49       ` Andrew Cagney
2002-05-16  6:59         ` Richard Earnshaw

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=200205151411.PAA23686@cam-mail2.cambridge.arm.com \
    --to=rearnsha@arm.com \
    --cc=Richard.Earnshaw@arm.com \
    --cc=ac131313@cygnus.com \
    --cc=eliz@is.elta.co.il \
    --cc=gdb@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